[JIRA] (JENKINS-36662) Downstream projects should not be triggered anymore after upstream project pom version is changed
Title: Message Title tsbx edited a comment on JENKINS-36662 Re: Downstream projects should not be triggered anymore after upstream project pom version is changed The issue is that *everytime* (not only the first time) jobA is rebuilt (for example, triggered by a commit), jobB is triggered ; even if projectA version has changed.If it was only the first build after the version change , it would be _not too bad_. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36662) Downstream projects should not be triggered anymore after upstream project pom version is changed
Title: Message Title tsbx commented on JENKINS-36662 Re: Downstream projects should not be triggered anymore after upstream project pom version is changed The issue is that everytime (not only the first time) jobA is rebuilt (for example, triggered by a commit), jobB is triggered ; even if projectA version has changed. If it was only the first build after the version, it would be not too bad. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36662) Downstream projects should not be triggered anymore after upstream project pom version is changed
Title: Message Title Arnaud Héritier commented on JENKINS-36662 Re: Downstream projects should not be triggered anymore after upstream project pom version is changed AFAIR the technical issue limitation here is that the trigger between Project A -> Project B is created or updated only after a build of Project B Thus when you are updating the version of project A, project B doesn't yet know that it changed thus the trigger launches project B But after a first useless build of Project B it should remove the trigger. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36662) Downstream projects should not be triggered anymore after upstream project pom version is changed
Title: Message Title . . created an issue Jenkins / JENKINS-36662 Downstream projects should not be triggered anymore after upstream project pom version is changed Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 2016/Jul/13 1:47 PM Environment: Jenkins 2.13 Maven Plugin 2.13 Priority: Major Reporter: . . Hello, Here is a two projects dependency graph (fixed version dependency; no version range used): test:projectB:jar:1.0-SNAPSHOT \- test:projectA:jar:1.0-SNAPSHOT:compile I have two jobs: jobA to build projectA (git: repoA, branch master), jobB to build projectB (git: repoB, branch master). Both are using git/notifyCommit?url to build on git push. Both are also configured with Build whenever a SNAPSHOT dependency is built. Jenkins links automatically the two jobs, and jobB becomes a downstream job of job A. This works perfectly, until I update the version of projectA. When projectA is modified with a new version (for instance 1.1-SNAPSHOT), and commited/pushed, jobA is built. But the new version is not detected (the jenkins "internal" dependency graph is not updated) and so projectB is still built after, even if now projectB does not depends on projectA version 1.1-SNAPSHOT. Here is the log after the version
