• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • core
    • Jenkins 1.652
      Ubuntu 15.10

      java version "1.7.0_95"
      OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-0ubuntu0.15.10.1)
      OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)

      The structure of runtime build parameters in the XML API for builds has changed in 1.652

      Retrieving XML for a job using /job/JobName/api/xml?depth=2

      In 1.651 the parameters are returned in the following structure:

      <build>
      <action>
      <parameter>
      <name>PARAM_NAME</name>
      <value>paramvalue</value>
      </parameter>
      </action>
      

      In 1.652 (and 1.653) the parameters are returned in the following structure:

      <build>
      <action>
      <name>PARAM_NAME</name>
      <value>paramvalue</value>
      </action>
      

      The <parameter> part of the output has disappeared. I do not see any reference to this in the changelog so I assume this is a regression and not an intentional change.

          [JENKINS-33546] Regression with build parameters in XML API

          Dominic Bishop created issue -
          Dominic Bishop made changes -
          Environment Original: Jenkins 1.652
          Ubuntu 15.10
          New: Jenkins 1.652
          Ubuntu 15.10

          java version "1.7.0_95"
          OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-0ubuntu0.15.10.1)
          OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode)

          Same problem for me.
          Sometime it's write <actions> (with a "s")

          Break my job to query sub-job informations.

          Boudoux Etienne added a comment - Same problem for me. Sometime it's write <actions> (with a "s") Break my job to query sub-job informations.
          Daniel Beck made changes -
          Labels New: regression
          Daniel Beck made changes -
          Link New: This issue is related to JENKINS-33605 [ JENKINS-33605 ]

          Daniel Beck added a comment -

          This is how the API looks like for me (attached screenshots, forgot to just grab the text).

          It's not just the missing "parameter" elements, there's also a separate "actions" wrapper for the cause, which used to be "action". ?tree=actions has the very weird output of:

          …
          <action/>
          <action/>
          <actions/>
          …

          Daniel Beck added a comment - This is how the API looks like for me (attached screenshots, forgot to just grab the text). It's not just the missing "parameter" elements, there's also a separate "actions" wrapper for the cause, which used to be "action". ?tree=actions has the very weird output of: … <action/> <action/> <actions/> …
          Daniel Beck made changes -
          Attachment New: Stapler 1.240.png [ 32214 ]
          Attachment New: Stapler 1.239.png [ 32215 ]
          Daniel Beck made changes -
          Priority Original: Major [ 3 ] New: Critical [ 2 ]
          Daniel Beck made changes -
          Assignee New: Kohsuke Kawaguchi [ kohsuke ]

          Daniel Beck added a comment - - edited

          Assigning to KK so this can be resolved at the same time as JENKINS-33605. Tempted to back out the Stapler update in the mean time, as its new features are not currently used.

          Daniel Beck added a comment - - edited Assigning to KK so this can be resolved at the same time as JENKINS-33605 . Tempted to back out the Stapler update in the mean time, as its new features are not currently used.

            vivek Vivek Pandey
            djb61 Dominic Bishop
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: