Compute build parameters on updated branch naming conventions #200
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
Signed-off-by: Dennis Behm <dennis.behm@de.ibm.com>
Signed-off-by: Dennis Behm <dennis.behm@de.ibm.com>
… test log Signed-off-by: Dennis Behm <dennis.behm@de.ibm.com>
|
Had a chat with @M-DLB about it, who is proposing a more simpler layout for the branches. Instead of multi segment, he is proposing
|
Signed-off-by: Dennis Behm <dennis.behm@de.ibm.com>
|
I have updated the scripts and followed your recommendations to name the feature branches. The currently implemented layout is listed below.
|
|
Please note that this PR improves the computation of the build parameter |
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.
As indicated in #193, the pipeline backend scripts need to use shorter branch names.
This PR is refreshing the computation of the build conventions:
F.E.H.R.