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.
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
Sync develop to master #270
Sync develop to master #270
Changes from 8 commits
1cc6d68
d107b2b
8c8675d
07e0577
a4c819d
b079096
ab083d8
5d9f0e1
217abaf
f5a532f
43161a2
acea202
57b4123
d7d8283
bfce6f8
8c3d7b1
3a1e559
1933cc3
36735e5
9eac965
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Since users will typically use the
build-image.sh
script directly, which calls thisDockerfile
, do we want to updatebuild-image.sh
to take a git branch as an argument, and then pass it as aGIT_BRANCH
arg intoDockerfile
?I suppose the same question can be asked for
DOCKER_ORG
andDOCKER_TAG
as well.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.
Or if this PR is only addressing the fix from an automated CI standpoint, we can create a separate story (or multiple) to fix it from a user standpoint.
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 they new arguments in the docker file will largely replace build-image.sh functionality that is responsible for setting org/tag for images.
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 am okay with merging this since that build-images.sh script needed manual edits to work correctly anyways (such as checkout scripts or Dockerfile edits).
I do agree we can create new story to modify pass in these arguments based on what
build-script.sh
sets the metada.