Details
-
Bug
-
Status: Closed (View Workflow)
-
Blocker
-
Resolution: Postponed
-
Jenkins 2.7.3 LTS
Multijob plugin version 1.22
Description
Jenkins project view does not show contents when it's a multijob project after upgrading to Jenkins 2.7.x :
Instead it show an error page with a stacktrace : (JellyTagException). See attachments.
Attachments
Issue Links
- duplicates
-
-
- Closed
-
- is duplicated by
-
-
- Closed
-
Activity
This is JENKINS-37300. I believe multijob removed the unsupported EZ templates code to solve that. Suggest this is closeable.
Kleber Souza
added a comment - I was having the same problem with Jenkins 2.19 with Multijob plugin 1.22. It's now working after downgrading the plugin to version 1.21.
Kleber Souza
added a comment - I was having the same problem with Jenkins 2.19 with Multijob plugin 1.22. It's now working after downgrading the plugin to version 1.21. 
Koen Franken
added a comment - Alternative to defining all parameters individually (which will be harder to find when also using custom predefined parameters on sub-jobs) is to re-enable the old "policy"...
Add -Dhudson.model.ParametersAction.keepUndefinedParameters=true to the JAVA_ARGS in /etc/default/jenkins.
Tested on Jenkins 2.22 with Multijob plugin 1.21.
Koen Franken
added a comment - Alternative to defining all parameters individually (which will be harder to find when also using custom predefined parameters on sub-jobs) is to re-enable the old "policy"...
Add -Dhudson.model.ParametersAction.keepUndefinedParameters=true to the JAVA_ARGS in /etc/default/jenkins.
Tested on Jenkins 2.22 with Multijob plugin 1.21. Hello, this is blocker problem for us. We upgrade jenkins to 2.7.4 and now we have problem with parameters (https://issues.jenkins-ci.org/browse/JENKINS-36124). But this build 1.22 doesn't works! What can I do? Is possible downgrade jenkins from 2.7.4 back to 1.651.1?
EDIT:
I found temporary solution.
I define all parameters to jenkins configuration -Dhudson.model.ParametersAction.safeParameters=$PARAMS
$PARAMS I find via this command:
for f in `find . -maxdepth 2 -name config.xml`; do (grep -i -a2 'ParameterDefinition' "$f" | grep name); done | cut -d '>' -f2 | cut -d '<' -f1 | sort | uniq
Jan Seidl
added a comment - - edited Hello, this is blocker problem for us. We upgrade jenkins to 2.7.4 and now we have problem with parameters ( https://issues.jenkins-ci.org/browse/JENKINS-36124 ). But this build 1.22 doesn't works! What can I do? Is possible downgrade jenkins from 2.7.4 back to 1.651.1?
EDIT:
I found temporary solution.
I define all parameters to jenkins configuration -Dhudson.model.ParametersAction.safeParameters=$PARAMS
$PARAMS I find via this command:
for f in `find . -maxdepth 2 -name config.xml`; do (grep -i -a2 'ParameterDefinition' "$f" | grep name); done | cut -d '>' -f2 | cut -d '<' -f1 | sort | uniq
Closing issue as part of tikal-multijob-plugin issues cleanup.
If still relevant, please open a matching issue in https://github.com/jenkinsci/tikal-multijob-plugin/issues (you can refer to this issue in its description)