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

JENKINS-34789 doesn't always prevent to have a release build triggering another job

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • maven-plugin
    • None

      cc fbelzunc

       

      create 1 maven-job with https://github.com/jenkins-demo/moduleA tag 1.0

      create 1 maven-job with https://github.com/jenkins-demo/moduleB branch release

      buildDependencyGraph called on hudson.maven.MavenModule@5f168cfa[module-b/com.mycompany.app:module-b][module-b/com.mycompany.app:module-b][relativePath:] with [ModuleDependency{groupId='com.mycompany.app', artifactId='module-a', version='1.0', plugin=false}]
May 04, 2017 8:11:11 PM FINER hudson.maven.MavenModule buildDependencyGraph
allModules: {ModuleDependency{groupId='com.mycompany.app', artifactId='module-b', version='1.0-SNAPSHOT', plugin=false}=hudson.maven.MavenModule@5f168cfa[module-b/com.mycompany.app:module-b][module-b/com.mycompany.app:module-b][relativePath:], ModuleDependency{groupId='com.mycompany.app', artifactId='module-a', version='1.0', plugin=false}=hudson.maven.MavenModule@77f0c98[module-a/com.mycompany.app:module-a][module-a/com.mycompany.app:module-a][relativePath:]} myParentsModules: {ModuleDependency{groupId='com.mycompany.app', artifactId='module-b', version='1.0-SNAPSHOT', plugin=false}=hudson.maven.MavenModule@5f168cfa[module-b/com.mycompany.app:module-b][module-b/com.mycompany.app:module-b][relativePath:]}
May 04, 2017 8:11:11 PM FINER hudson.maven.MavenModule buildDependencyGraph
adding hudson.maven.AbstractMavenProject$MavenModuleDependency@c51224ca[hudson.maven.MavenModuleSet@334bbfbe[module-a]->hudson.maven.MavenModuleSet@2943dc41[module-b]]
May 04, 2017 8:11:11 PM FINER hudson.maven.MavenModule buildDependencyGraph
finished adding to dependency graph

      A trigger A -> B is created while moduleA produces a RELEASE artifact and moduleB consumes this release

      But the trigger isn't used

      [JENKINS] Archiving /Users/arnaud/CloudBees/Support/Environments/cjt-2.46.2.1/jenkins-home/workspace/module-a/pom.xml to com.mycompany.app/module-a/1.0/module-a-1.0.pom
[JENKINS] Archiving /Users/arnaud/CloudBees/Support/Environments/cjt-2.46.2.1/jenkins-home/workspace/module-a/target/module-a-1.0.jar to com.mycompany.app/module-a/1.0/module-a-1.0.jar
channel stopped
Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered
Finished: SUCCESS

      Reconfigured these jobs to build the branches develop, and launch them

      Then come back to the original tag 1.0 and release branch

      May 04, 2017 7:44:52 PM FINER hudson.maven.MavenModule buildDependencyGraph
buildDependencyGraph called on hudson.maven.MavenModule@2106547[module-b/com.mycompany.app:module-b][module-b/com.mycompany.app:module-b][relativePath:] with [ModuleDependency{groupId='com.mycompany.app', artifactId='module-a', version='1.0', plugin=false}]
May 04, 2017 7:44:52 PM FINER hudson.maven.MavenModule buildDependencyGraph
allModules: {ModuleDependency{groupId='com.mycompany.app', artifactId='module-a2', version='2.0-SNAPSHOT', plugin=false}=hudson.maven.MavenModule@5a3194a8[module-a/com.mycompany.app:module-a2][module-a/com.mycompany.app:module-a2][relativePath:module-a2], ModuleDependency{groupId='com.mycompany.app', artifactId='module-b', version='1.0-SNAPSHOT', plugin=false}=hudson.maven.MavenModule@2106547[module-b/com.mycompany.app:module-b][module-b/com.mycompany.app:module-b][relativePath:], ModuleDependency{groupId='com.mycompany.app', artifactId='module-a', version='1.0', plugin=false}=hudson.maven.MavenModule@5f5c83e2[module-a/com.mycompany.app:module-a][module-a/com.mycompany.app:module-a][relativePath:], ModuleDependency{groupId='com.mycompany.app', artifactId='module-b1', version='2.0-SNAPSHOT', plugin=false}=hudson.maven.MavenModule@3f839228[module-b/com.mycompany.app:module-b1][module-b/com.mycompany.app:module-b1][relativePath:module-b1], ModuleDependency{groupId='com.mycompany.app', artifactId='module-a1', version='2.0-SNAPSHOT', plugin=false}=hudson.maven.MavenModule@24275100[module-a/com.mycompany.app:module-a1][module-a/com.mycompany.app:module-a1][relativePath:module-a1], ModuleDependency{groupId='com.mycompany.app', artifactId='module-b2', version='2.0-SNAPSHOT', plugin=false}=hudson.maven.MavenModule@693f27bb[module-b/com.mycompany.app:module-b2][module-b/com.mycompany.app:module-b2][relativePath:module-b2]} myParentsModules: {ModuleDependency{groupId='com.mycompany.app', artifactId='module-b', version='1.0-SNAPSHOT', plugin=false}=hudson.maven.MavenModule@2106547[module-b/com.mycompany.app:module-b][module-b/com.mycompany.app:module-b][relativePath:], ModuleDependency{groupId='com.mycompany.app', artifactId='module-b1', version='2.0-SNAPSHOT', plugin=false}=hudson.maven.MavenModule@3f839228[module-b/com.mycompany.app:module-b1][module-b/com.mycompany.app:module-b1][relativePath:module-b1], ModuleDependency{groupId='com.mycompany.app', artifactId='module-b2', version='2.0-SNAPSHOT', plugin=false}=hudson.maven.MavenModule@693f27bb[module-b/com.mycompany.app:module-b2][module-b/com.mycompany.app:module-b2][relativePath:module-b2]}
May 04, 2017 7:44:52 PM FINER hudson.maven.MavenModule buildDependencyGraph
adding hudson.maven.AbstractMavenProject$MavenModuleDependency@3998e2[hudson.maven.MavenModuleSet@429eb748[module-a]->hudson.maven.MavenModuleSet@3f712f3[module-b]]
May 04, 2017 7:44:52 PM FINER hudson.maven.MavenModule buildDependencyGraph
finished adding to dependency graph

      The trigger is created and actif, probably because jenkins can see previous artifacts related to these jobs in SNAPSHOT

      [JENKINS] Archiving /Users/arnaud/CloudBees/Support/Environments/cjt-2.46.2.1/jenkins-home/workspace/module-a/pom.xml to com.mycompany.app/module-a/1.0/module-a-1.0.pom
[JENKINS] Archiving /Users/arnaud/CloudBees/Support/Environments/cjt-2.46.2.1/jenkins-home/workspace/module-a/target/module-a-1.0.jar to com.mycompany.app/module-a/1.0/module-a-1.0.jar
channel stopped
Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered
Triggering a new build of module-b
Finished: SUCCESS

       

      I don't think it is expected if I understand JENKINS-34789, we should just not add the trigger

       

            Unassigned Unassigned
            aheritier Arnaud Héritier
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: