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

Trigger "Build after other projects" does not work

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • maven-plugin
    • None

      Upstream-Projects are not recognized by Maven-plugin, when defined in a Maven-job by "Build after other projects are build":

      Setup "job A" as Freestyle Project
      Setup "job B" as Freestyle Project and set "job A" as trigger (Status shows job A as Upstream Project)

      Setup "job Maven-B" as Maven Project and set "job A" as trigger (Status does not show any upstream project)

      When "job A" is build and finishes, "job B" is triggered, but not "job Maven-B"

      You can make "job Maven-B" triggered by "job A" by setting it as a Post-Build-Action in "job A"

          [JENKINS-23686] Trigger "Build after other projects" does not work

          Christian Langmann created issue -
          Christian Langmann made changes -
          Link New: This issue is related to JENKINS-16956 [ JENKINS-16956 ]

          Hugo de Paix de Coeur added a comment -

          Similar behavior spotted here (Jenkins #570, #571).
          This is a critical bug for 1-n jobs triggering workflows.

          Hugo de Paix de Coeur added a comment - Similar behavior spotted here (Jenkins #570, #571). This is a critical bug for 1-n jobs triggering workflows.
          Jesse Glick made changes -
          Link New: This issue is related to JENKINS-22397 [ JENKINS-22397 ]
          Jesse Glick made changes -
          Assignee New: Jesse Glick [ jglick ]
          Jesse Glick made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]

          SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Jesse Glick
          Path:
          src/main/java/hudson/maven/MavenModuleSet.java
          http://jenkins-ci.org/commit/maven-plugin/9ac66ee95d401330f99e1c0fd1fecc35e4c61227
          Log:
          [FIXED JENKINS-23686] Fix of JENKINS-22397 not automatically available to overriders of buildDependencyGraph unless they were using 1.558+ and calling super.

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Jesse Glick Path: src/main/java/hudson/maven/MavenModuleSet.java http://jenkins-ci.org/commit/maven-plugin/9ac66ee95d401330f99e1c0fd1fecc35e4c61227 Log: [FIXED JENKINS-23686] Fix of JENKINS-22397 not automatically available to overriders of buildDependencyGraph unless they were using 1.558+ and calling super.

          Jesse Glick added a comment -

          Ought to work in next version of the plugin. (Did not have time to write a test to prove it.)

          Jesse Glick added a comment - Ought to work in next version of the plugin. (Did not have time to write a test to prove it.)
          Jesse Glick made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Progress [ 3 ] New: Resolved [ 5 ]
          Steffen Sledz made changes -
          Link New: This issue is related to JENKINS-25758 [ JENKINS-25758 ]

            jglick Jesse Glick
            christianlangmann Christian Langmann
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: