-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Quick: Update Makefile to support git branches #801
Merged
Merged
Changes from 2 commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@rstijerina, I must wait until the end of the build (which can be long) before I see
docker tag
output.1How could I see that output sooner? So I could copy-paste to Core-Portal-Deployments during build.
+ echo "Building '`$(DOCKER_IMAGE_BRANCH)`'…" docker build -t $(DOCKER_IMAGE) \
Footnotes
docker tag taccwma/core-cms:783b7fb taccwma/core-cms:test-update-makefile-support-branch-tags
↩There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@wesleyboar Good suggestion. We could add
DOCKER_IMAGE_BRANCH=...
andecho "Building '$(DOCKER_IMAGE_BRANCH)'…"
to the Jenkins build as wellThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I dunno about putting same script snippet in Makefile and Jenkins. If after using this a while, I feel the urge, then I'll think on a shared code solution or give in to copy-paste.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the jenkins build console output, you can see what the tag is going to be at the very top (before STEP 1 begins) in these lines (copied from your build job above - https://jenkins01.tacc.utexas.edu/job/Core_CMS_Build/1375/console):
then a few lines later:
which is the same things you will see in STEP 25:
and reflects what you get at the end of the build pipe if it is successful:
Does that help?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this doesn't include the special char replacement done by the
DOCKER_IMAGE_BRANCH
varThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like this (in the beginning):
still matches this output (at the very end):
Is that because Wes names things well and therefore there was no real conversion of special characters from the value in the
.env
file (CMS_TAG=test-update-makefile-support-branch-tags # v4.8.0 candidate
)?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But if the branch was
test/update-makefile-support-branch-tags
, that would not match with it being converted totest-update-makefile-support-branch-tags
by theDOCKER_IMAGE_BRANCH
varyeah, exactly
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@taoteg was right to look at other lines. What I want (most of the time) is available reliably enough via:
Not a branch name, but it matches when I build via tag.
When I next need to build by branch, I [may return to] this.