You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+32-3Lines changed: 32 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,8 +19,9 @@ This plugin solves a few specific issues common in consolidated Hudson/Jenkins C
19
19
1. Ensure the developers are following the (git branching) project version rules, and fail the build if they are not.
20
20
2. Enable the maven-deploy-plugin to target a snapshots, test-releases, and releases repository.
21
21
3._Copy_ (rather than rebuild) the tested artifacts from the test-releases repository to the release repository, without doing a full project rebuild from the master branch.
22
-
4. Reliably tag deploy builds from the 'master' branch
23
-
5. Enable split 'deploy' vs. 'deliver' maven CI job configuration, without rebuilding artifacts for the 'deliver' phase.
22
+
4. Set arbitrary project properties based upon the type of GIT branch being built.
23
+
5. Reliably tag deploy builds from the 'master' branch
24
+
6. Enable split 'deploy' vs. 'deliver' maven CI job configuration, without rebuilding artifacts for the 'deliver' phase.
24
25
25
26
In addition to supporting these goals for the project, this plugin does it in a manner that tries to be as effortless (yet configurable) as possible.
26
27
If you use non-standard gitflow branch names (emer instead of hotfix), this plugin supports that. If you don't want to do version enforcement, this plugin supports that.
@@ -63,6 +64,21 @@ All of the solutions to these issues are implemented independently in different
0 commit comments