Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-38053

JellyTagException on Multijob project view with Jenkins 2.7.3 LTS

    • Icon: Bug Bug
    • Resolution: Postponed
    • Icon: Blocker Blocker
    • multijob-plugin
    • Jenkins 2.7.3 LTS
      Multijob plugin version 1.22

      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.

          [JENKINS-38053] JellyTagException on Multijob project view with Jenkins 2.7.3 LTS

          Is this a duplicate of JENKINS-37300 ?

          Christian Höltje added a comment - Is this a duplicate of JENKINS-37300 ?

          Not exactly the same stacktrace, but
          downgrading to plugin version 1.21 solves the issue !

          Jurgen Van Bouchaute added a comment - Not exactly the same stacktrace, but downgrading to plugin version 1.21 solves the issue !

          Dirk Kuypers added a comment -

          I am experiencing the same stack trace on Jenkins 2.21.

          Dirk Kuypers added a comment - I am experiencing the same stack trace on Jenkins 2.21.

          Caleb Mayeux added a comment -

          Also seeing the same here on Jenkins 1.642.3 and 1.642.18.3. Also don't see issue on 1.21.

          Tried making a fresh multijob, and the job screen appears with no issue. The stacktrace appears when I add a "Trigger/call builds on other projects" build step from the Parameterized Trigger Plugin to a Multijob. Take it out, and the job screen doesn't have a stacktrace. Hopefully that tidbit helps narrow down the issue.

          Caleb Mayeux added a comment - Also seeing the same here on Jenkins 1.642.3 and 1.642.18.3. Also don't see issue on 1.21. Tried making a fresh multijob, and the job screen appears with no issue. The stacktrace appears when I add a "Trigger/call builds on other projects" build step from the Parameterized Trigger Plugin to a Multijob. Take it out, and the job screen doesn't have a stacktrace. Hopefully that tidbit helps narrow down the issue.

          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
          

          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

          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.

          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.

          Marc Carter added a comment -

          This is JENKINS-37300. I believe multijob removed the unsupported EZ templates code to solve that. Suggest this is closeable.

          Marc Carter added a comment - This  is JENKINS-37300 . I believe multijob removed the unsupported EZ templates code to solve that. Suggest this is closeable.

          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)

          Yoram Michaeli added a comment - 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)

            Unassigned Unassigned
            jvanbouchaute Jurgen Van Bouchaute
            Votes:
            4 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: