-
Bug
-
Resolution: Fixed
-
Major
-
None
When the TriggerBuilder is used, the downstream jobs report the parent job as their upstream, but the parent job doesn't report the TriggerBuilder-built jobs as downstream jobs. This can make navigating the resulting build tree a pain.
- is related to
-
JENKINS-5184 No up/downstream indication when using Parameterized Build Trigger plugin
-
- Resolved
-
[JENKINS-11082] TriggerBuilder builds should be listed as downstream builds
Link |
New:
This issue is related to |
Assignee | Original: huybrechts [ huybrechts ] | New: Kohsuke Kawaguchi [ kohsuke ] |
Assignee | Original: Kohsuke Kawaguchi [ kohsuke ] | New: Andrew Bayer [ abayer ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Workflow | Original: JNJira [ 141292 ] | New: JNJira + In-Review [ 189544 ] |
Code changed in jenkins
User: Andrew Bayer
Path:
src/main/java/hudson/plugins/parameterizedtrigger/TriggerBuilder.java
http://jenkins-ci.org/commit/parameterized-trigger-plugin/a23dfab2775e2ffb84d5aa73da4533e971c690cb
Log:
[FIXED JENKINS-11082, FIXED JENKINS-9263, FIXED JENKINS-5184] Builds
triggered as build steps will now show up in the dependency graph.