Details
-
Type:
Bug
-
Status: Open (View Workflow)
-
Priority:
Major
-
Resolution: Unresolved
-
Component/s: core
-
Labels:
-
Environment:Linux 32 bit , Upgraded from Jenkins 1.504 to 1.514 by replacing the war file.
-
Similar Issues:
Description
Previously on 1.504 when you looked at a project it showed you "Downstream" and "Upstream" jobs in the project view. Now on 1.514 it does not. If I look at the Dependency Graph, almost all of my jobs are unlinked, Also when looking at the build pipeline it now fails to recognise that the jobs are linked together, so only shows the single job at the start of the pipeling. See attached doc for example
Attachments
Activity
Paul Carr
created issue -
Paul Carr
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Description | Previously on 1.504 when you looked at a project it showed you "Downstream" and "Upstream" jobs in the project view. Now on 1.515 it does not. If I look at the Dependency Graph, almost all of my jobs are unlinked, Also when looking at the build pipeline it now fails to recognise that the jobs are linked together, so only shows the single job at the start of the pipeling. See attached doc for example | Previously on 1.504 when you looked at a project it showed you "Downstream" and "Upstream" jobs in the project view. Now on 1.514 it does not. If I look at the Dependency Graph, almost all of my jobs are unlinked, Also when looking at the build pipeline it now fails to recognise that the jobs are linked together, so only shows the single job at the start of the pipeling. See attached doc for example |
| Environment | Linux 32 bit , Upgraded from Jenkins 1.504 to 1.515 by replacing the war file. | Linux 32 bit , Upgraded from Jenkins 1.504 to 1.514 by replacing the war file. |
Paul Carr
made changes -
| Attachment | DependencyWorking.png [ 23647 ] |
I've tested this further and it seems there's two ways to trigger a downstream project. One is as a PostBuildStep , where you can choose to block or not, and the other is a PostBuildAction. If doing it as a PostBuildStep, it is not recognized by Jenkins as a dependency, and does not appear in the Dependency View Plugin or the Pipeline plugin. If you add a PostBuildAction of "Trigger Parameterized Build on other projects" it DOES get recognized as a downstream dependency , and appears in the afforementioned plugins. So, is this intentional, or an oversight. We have been mainly using PostBuildSteps, as it allows you to block and wait......but now .... as you've seen ....our Dependency View is somewhat anaemic.
Paul Carr
added a comment - I've tested this further and it seems there's two ways to trigger a downstream project. One is as a PostBuildStep , where you can choose to block or not, and the other is a PostBuildAction. If doing it as a PostBuildStep, it is not recognized by Jenkins as a dependency, and does not appear in the Dependency View Plugin or the Pipeline plugin. If you add a PostBuildAction of "Trigger Parameterized Build on other projects" it DOES get recognized as a downstream dependency , and appears in the afforementioned plugins. So, is this intentional, or an oversight. We have been mainly using PostBuildSteps, as it allows you to block and wait......but now .... as you've seen ....our Dependency View is somewhat anaemic. Do you know whether this has changed since 1.514, what's the current state of this issue?
| Labels | Dependency Pipeline | downstream |
| Workflow | JNJira [ 149242 ] | JNJira + In-Review [ 177296 ] |
The DependencyWorking.png file shows what the Dependency Graph used to give us at version 1.504