Job generator plugin was last released 8 years ago. The last commit to the repository was also 8 years ago. Probably best to convert your jobs to use Jenkins Pipeline.
If the plugin is crucial to you, you could adopt the plugin, modify it to support the current Jenkins versions, and release a new version. The "Contributing to Open Source" workshop may be helpful, including the 5 part video series.
The plugin also contains a known security vulnerability. Really best to convert your jobs to use Jenkins Pipeline.
Mark Waite
added a comment - - edited Job generator plugin was last released 8 years ago. The last commit to the repository was also 8 years ago. Probably best to convert your jobs to use Jenkins Pipeline.
If the plugin is crucial to you, you could adopt the plugin, modify it to support the current Jenkins versions, and release a new version. The "Contributing to Open Source" workshop may be helpful, including the 5 part video series.
The plugin also contains a known security vulnerability. Really best to convert your jobs to use Jenkins Pipeline.
FWIW, I found a workaround to this problem. I created a node called 'master' on the Jenkins master.
Generator jobs now work without updating the plugin. It appears the plugin really wants the node name to be 'master' and the label 'master' isn't quite enough.
I have not explored the plugin to see why this occurs.
You may need to adjust the number of executors in 'Built-in Node' and 'master' since you now have two nodes on the same machine.
Eric Boehm
added a comment - FWIW, I found a workaround to this problem. I created a node called 'master' on the Jenkins master.
Generator jobs now work without updating the plugin. It appears the plugin really wants the node name to be 'master' and the label 'master' isn't quite enough.
I have not explored the plugin to see why this occurs.
You may need to adjust the number of executors in 'Built-in Node' and 'master' since you now have two nodes on the same machine.
Unassigned
jenkins upv
Votes:
0Vote for this issue
Watchers:
3Start watching this issue
Created:
Updated:
{"errorMessages":["jqlTooComplex"],"errors":{}}
[{"id":-1,"name":"My open issues","jql":"assignee = currentUser() AND resolution = Unresolved order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":true},{"id":-2,"name":"Reported by me","jql":"reporter = currentUser() order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":true},{"id":-4,"name":"All issues","jql":"order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-5,"name":"Open issues","jql":"resolution = Unresolved order by priority DESC,updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-9,"name":"Done issues","jql":"statusCategory = Done order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-3,"name":"Viewed recently","jql":"issuekey in issueHistory() order by lastViewed DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-6,"name":"Created recently","jql":"created >= -1w order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-7,"name":"Resolved recently","jql":"resolutiondate >= -1w order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-8,"name":"Updated recently","jql":"updated >= -1w order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false}]
Job generator plugin was last released 8 years ago. The last commit to the repository was also 8 years ago. Probably best to convert your jobs to use Jenkins Pipeline.
If the plugin is crucial to you, you could adopt the plugin, modify it to support the current Jenkins versions, and release a new version. The "Contributing to Open Source" workshop may be helpful, including the 5 part video series.
The plugin also contains a known security vulnerability. Really best to convert your jobs to use Jenkins Pipeline.