JENKINS-24090 Re-implement "Append Jenkins Build Number" Option #24
Conversation
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
|
plugins » m2release-plugin #44 SUCCESS |
|
Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We find it very useful to append the Jenkins Build Number to the release version and loosing this feature when trying to upgrade from an old Hudson version to the latest Jenkins creates issues for us with our current workflow. I have re-implemented this with a couple of improvements.
See https://issues.jenkins-ci.org/browse/JENKINS-24090