-
Notifications
You must be signed in to change notification settings - Fork 1.5k
fix issues with build-images script #6145
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
Conversation
fetch commit_sha from source_code_directory (don't assume we're in the source tree anymore), allow custom tag (if a parameter is passed in as $1) update README.md
AWS CodeBuild CI Report for macOS Catalina 10.15
|
|
GitHub doesn't allow me to comment on lines 171-173 in "packaging/docker/build-images.sh", so posting this comment here. Would you please move lines 171-173 to come after line 176 (my YCSB run picked up the images without any issue after I made that change)? Thanks! |
liquid-helium
left a comment
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.
Nice! Thanks Aaron!
AWS CodeBuild CI Report for Linux CentOS 7
|
|
Thanks! |
@sbodagala I verified that the |
copy packaging/docker to PROJECT_BINARY_DIR (undoing part of #5994), fetch commit_sha from source_code_directory (don't assume we're in the source tree anymore), allow custom tag (if a parameter is passed in as $1) update README.md
copy packaging/docker to PROJECT_BINARY_DIR (undoing part of #5994), fetch commit_sha from source_code_directory (don't assume we're in the source tree anymore), allow custom tag (if a parameter is passed in as $1) update README.md
copy packaging/docker to PROJECT_BINARY_DIR (undoing part of #5994),
fetch commit_sha from source_code_directory (don't assume we're in the source tree anymore),
allow custom tag (if a parameter is passed in as $1)
update README.md
Code-Reviewer Section
The general guidelines can be found here.
Please check each of the following things and check all boxes before accepting a PR.
For Release-Branches
If this PR is made against a release-branch, please also check the following:
release-branchormasterif this is the youngest branch)