Open
Conversation
Member
|
Hi @hipstersmoothie, if you'd still like this change to be merged, could you please rebase on latest |
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
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.
Trying to use env-ci in a multi-branch pipeline jenkins project. The main problem I have run into is that jenkins will make it's own branch when building (e.g PR-123). This is not the name of the actual branch it's building, and anything that tries to use the
branchname will failhttps://ci.eclipse.org/webtools/env-vars.html/
Solution
Use the
CHANGE_BRANCHenv var