Build notes file path #26
Open
Conversation
This file contains hidden or 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
… to the build notes field. The default path is $WORKSPACE/BUILD_NOTES. It will search for the file exactly to start with and will prepend $WORSKSPACE to the given path if it is not found.
|
Jenkins » testflight-plugin #62 SUCCESS |
Member
|
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
3 participants
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.
I found that it was easier to manage the build notes as a file in my repository rather than having to go into Jenkins to write them into the Job's configuration field. This way they are version controlled and can be created in the IDE or other editor along with the code. I realise it may be possible to do this using environment variable hackery, but I couldn't get newlines to work with the EnvInject plugin, so this ended up being quicker and I think nicer.
It will look for a BUILD_NOTES file in the workspace root by default, or if a file is given it will look for that first on the file system, then inside the workspace.