Details
-
New Feature
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
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
samodelkin
created issue -
mdonohue
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Resolution | Won't Fix [ 2 ] | |
| Status | Open [ 1 ] | Closed [ 6 ] |
samodelkin
made changes -
| Resolution | Won't Fix [ 2 ] | |
| Status | Closed [ 6 ] | Reopened [ 4 ] |
mdonohue
made changes -
| Resolution | Won't Fix [ 2 ] | |
| Status | Reopened [ 4 ] | Closed [ 6 ] |
mdonohue
made changes -
| Resolution | Won't Fix [ 2 ] | |
| Status | Closed [ 6 ] | Reopened [ 4 ] |
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 |
| Assignee | mindless [ mindless ] |
| Status | Reopened [ 4 ] | In Progress [ 3 ] |
| Resolution | Fixed [ 1 ] | |
| Status | In Progress [ 3 ] | Resolved [ 5 ] |
| Status | Resolved [ 5 ] | Closed [ 6 ] |
| Workflow | JNJira [ 135158 ] | JNJira + In-Review [ 203302 ] |