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

Downstream Dependency has broken, Also breaks Dependency Graph Plugin, and Build Pipeline Plugin

    XMLWordPrintable

    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

        1. DependencyWorking.png
          227 kB
          Paul Carr
        2. JenkinsDependencyProblem.odt
          428 kB
          Paul Carr

          Activity

          Hide
          paulca Paul Carr added a comment -

          The DependencyWorking.png file shows what the Dependency Graph used to give us at version 1.504

          Show
          paulca Paul Carr added a comment - The DependencyWorking.png file shows what the Dependency Graph used to give us at version 1.504
          Hide
          paulca 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.

          Show
          paulca 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.
          Hide
          danielbeck Daniel Beck added a comment -

          Do you know whether this has changed since 1.514, what's the current state of this issue?

          Show
          danielbeck Daniel Beck added a comment - Do you know whether this has changed since 1.514, what's the current state of this issue?

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            paulca Paul Carr
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated: