• Icon: New Feature New Feature
    • Resolution: Fixed
    • Icon: Major Major
    • core
    • None

      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.

          [JENKINS-5074] Detailed cause information in XML API

          samodelkin created issue -
          mdonohue made changes -
          Resolution New: Won't Fix [ 2 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]
          samodelkin made changes -
          Resolution Original: Won't Fix [ 2 ]
          Status Original: Closed [ 6 ] New: Reopened [ 4 ]
          mdonohue made changes -
          Resolution New: Won't Fix [ 2 ]
          Status Original: Reopened [ 4 ] New: Closed [ 6 ]
          mdonohue made changes -
          Resolution Original: Won't Fix [ 2 ]
          Status Original: Closed [ 6 ] New: Reopened [ 4 ]
          mdonohue made changes -
          Component/s New: core [ 15593 ]
          Description Original: 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.
          New: 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 Original: Ability to pass job information from upstream to downstream projects New: Detailed cause information in XML API
          Alan Harder made changes -
          Assignee New: Alan Harder [ mindless ]
          Alan Harder made changes -
          Status Original: Reopened [ 4 ] New: In Progress [ 3 ]
          SCM/JIRA link daemon made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Progress [ 3 ] New: Resolved [ 5 ]
          Andrew Bayer made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 135158 ] New: JNJira + In-Review [ 203302 ]

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

              Created:
              Updated:
              Resolved: