Details
-
Type:
Improvement
-
Status: Closed (View Workflow)
-
Priority:
Minor
-
Resolution: Duplicate
-
Component/s: pipeline-maven-plugin
-
Labels:None
-
Similar Issues:
Description
In our CI we build master and maintenance branches and every pull request of each repository.
With snapshotDependency trigger, a build on a master branch can trigger builds on PR branches. This is not wanted
JENKINS-46511 will avoid downstream jobs coming from a PR (because we just "verify", not "deploy" a PR), but the problem will still be there on master or maintenance branches, which are "deploy"
Attachments
Issue Links
- is related to
-
-
- Closed
-
Activity
Cyrille Le Clerc sorry for being silent so long
It seems I will close this issue, since ignoreUpstreamTriggers and skipDownstreamTriggers will help with my scenario (I misunderstood how they works)
But I need more time to test all of this 
benoit guerin
added a comment - Cyrille Le Clerc sorry for being silent so long
It seems I will close this issue, since ignoreUpstreamTriggers and skipDownstreamTriggers will help with my scenario (I misunderstood how they works)
But I need more time to test all of this benoit guerin can you please test pipeline-maven-3.0.1-beta-1.jar and the downstream trigger based on the Maven lifecycle threshold.
Regarding your "maintenance branches", I don't catch why they use the same snapshot versions as the "master" branch and cause undesired triggers. Could you please detail?
The default threshold is "deploy" which seems to meet your goals. You can change it to "package" or to "install".
It is all working fine. In fact, during my tests, I met JENKINS-46368
benoit guerin
added a comment - It is all working fine. In fact, during my tests, I met JENKINS-46368 Thanks benoit guerin
benoit guerin can you please detail more your use case? Can you provide a sample Jenkinsfile and explain what would be the branches and PRs of the applications and which you would not like to see triggering downstream jobs.