Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #98 from jenkinsci/JENKINS-46511
[JENKINS-46511] Only trigger downstream pipelines if maven builds reach a threshold lifecycle phase
- Loading branch information
Showing
10 changed files
with
819 additions
and
1,141 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
24 changes: 24 additions & 0 deletions
24
...sci/plugins/pipeline/maven/publishers/PipelineGraphPublisher/help-lifecycleThreshold.html
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Original file line | Diff line number | Diff line change |
---|---|---|---|
@@ -0,0 +1,24 @@ | |||
<div> | |||
<p> | |||
Threshold to trigger downstream pipelines based on the <a href="https://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html">Maven lifecycle</a> | |||
phase successfully reached during the Maven execution. | |||
</p> | |||
<p> | |||
If "install" is selected then downstream pipelines will be triggered for "<code>mvn clean install</code>", "<code>mvn clean deploy</code>" | |||
but NOT "<code>mvn clean verify</code>" or "<code>mvn clean package</code>". | |||
</p> | |||
|
|||
<h2>Example</h2> | |||
<p>Configure a Jenkins Multibranch Pipeline with | |||
<ul> | |||
<li>Threshold: "<code>deploy</code>"</li> | |||
<li>execution of "<code>mvn clean deploy</code>" on branches (incl. master) and execution of "<code>mvn clean | |||
verify</code> on pull requests</li> | |||
</ul> | |||
So that: | |||
<ul> | |||
<li>The builds of branches (incl. "master") would upload the generated jar/war file to your enterprise Maven repository and would trigger downstream pipelines</li> | |||
<li>The builds of pull request would only build the package but NOT upload the generated jar/war file to your enterprise Maven repository and would NOT trigger downstream pipelines</li> | |||
</ul> | |||
</p> | |||
</div> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.