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

Detailed cause information in XML API

    XMLWordPrintable

Details

    • New Feature
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • core
    • None

    Description

      The XML API only gives a text blob for the upstream cause:
      <action><cause><shortDescription>Started by upstream project "blah" build number 62</shortDescription></cause></action>

      It would be nice to have structured access to the data.

      Attachments

        Activity

          Ascending order - Click to sort in descending order
          samodelkin samodelkin created issue -
          mdonohue mdonohue added a comment - - edited

          My original comment quoted below makes less sense, now that the problem has been refined

          You can query the XML api to figure this out.
          http://n4.nabble.com/How-can-I-tell-what-triggered-a-build-td383536.html

          The upstream information is more rich than can easily be expressed in an environment variable. There's the job name and number, as well as parameters. Also, there can be multiple upstream jobs.

          mdonohue mdonohue added a comment - - edited My original comment quoted below makes less sense, now that the problem has been refined You can query the XML api to figure this out. http://n4.nabble.com/How-can-I-tell-what-triggered-a-build-td383536.html The upstream information is more rich than can easily be expressed in an environment variable. There's the job name and number, as well as parameters. Also, there can be multiple upstream jobs.
          mdonohue mdonohue made changes -
          Field Original Value New Value
          Resolution Won't Fix [ 2 ]
          Status Open [ 1 ] Closed [ 6 ]
          samodelkin samodelkin added a comment -

          Can you add elements for upstream job name and build number, please?
          Currently I have to parse them out from cause/shortDescription. This is fragile (format can change) and is not convenient (especially in shell scripts).

          samodelkin samodelkin added a comment - Can you add elements for upstream job name and build number, please? Currently I have to parse them out from cause/shortDescription. This is fragile (format can change) and is not convenient (especially in shell scripts).
          samodelkin samodelkin made changes -
          Resolution Won't Fix [ 2 ]
          Status Closed [ 6 ] Reopened [ 4 ]
          samodelkin samodelkin added a comment -

          And still it is not possible to use API to set downstream build parameters, e.g. to set TAG parameter and use it in SVN checkout step.

          samodelkin samodelkin added a comment - And still it is not possible to use API to set downstream build parameters, e.g. to set TAG parameter and use it in SVN checkout step.
          mdonohue mdonohue added a comment -

          I suggest taking your problem description to the users mailing list to see what others have done.

          mdonohue mdonohue added a comment - I suggest taking your problem description to the users mailing list to see what others have done.
          mdonohue mdonohue made changes -
          Resolution Won't Fix [ 2 ]
          Status Reopened [ 4 ] Closed [ 6 ]
          mdonohue mdonohue added a comment -

          I see. The cause XML data doesn't have anything beside a short description

          mdonohue mdonohue added a comment - I see. The cause XML data doesn't have anything beside a short description
          mdonohue mdonohue made changes -
          Resolution Won't Fix [ 2 ]
          Status Closed [ 6 ] Reopened [ 4 ]
          mdonohue mdonohue made changes -
          Component/s core [ 15593 ]
          Description Use-case is:
          - There is a set of upstream builds that build a project in different flavors (nightly clean build, CI on-commit build, release build)
          - There is a downstream "test" job that gets the build and runs integration tests
          - "test" job build steps should know upstream job name and build number in order to get proper build from SCP repository or from NFS/SMB shares or from HTTP. Upstream job name and build number should be at least available as environment variables during build steps execution.

          Or, they should be available for use in default values for downstream build parameters (if downstream build is parameterized): e.g. it should be possible to create a parameter "UPSTREAM_JOB_NAME" and set its default value to ${UPSTREAM_JOB_NAME}. When the downstream job is started manually this parameter has empty value by default. If it is triggered by upstream job, upstream job name should be properly substituted.           		The XML API only gives a text blob for the upstream cause:
          <action><cause><shortDescription>Started by upstream project "blah" build number 62</shortDescription></cause></action>

          It would be nice to have structured access to the data.
          Summary Ability to pass job information from upstream to downstream projects Detailed cause information in XML API
          mindless Alan Harder made changes -
          Assignee mindless [ mindless ]
          mindless Alan Harder made changes -
          Status Reopened [ 4 ] In Progress [ 3 ]
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in hudson
          User: : mindless
          Path:
          trunk/hudson/main/core/src/main/java/hudson/model/Cause.java
          trunk/www/changelog.html
          http://fisheye4.cenqua.com/changelog/hudson/?cs=24655
          Log:
          [FIXED JENKINS-5074] expose upstream cause details via remote API

          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in hudson User: : mindless Path: trunk/hudson/main/core/src/main/java/hudson/model/Cause.java trunk/www/changelog.html http://fisheye4.cenqua.com/changelog/hudson/?cs=24655 Log: [FIXED JENKINS-5074] expose upstream cause details via remote API
          scm_issue_link SCM/JIRA link daemon made changes -
          Resolution Fixed [ 1 ]
          Status In Progress [ 3 ] Resolved [ 5 ]
          mdonohue mdonohue added a comment -

          Fast!

          mdonohue mdonohue added a comment - Fast!
          abayer Andrew Bayer made changes -
          Status Resolved [ 5 ] Closed [ 6 ]
          rtyler R. Tyler Croy made changes -
          Workflow JNJira [ 135158 ] JNJira + In-Review [ 203302 ]

          People

            mindless Alan Harder
            samodelkin samodelkin
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: