Update Build-Deploy Script to support SC Manifest Builds #889
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
|
/retest |
casey-williams-rh
force-pushed
the
update-build-deploy-sc-support
branch
from
79295cd
to
a7b1c92
Compare
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.
This PR updates the
build_deployscript to checks if the current Git branch$GIT_BRANCHisorigin/security-compliance. If the condition is true, meaning the current branch isorigin/security-compliance, it sets theIMAGE_TAGvariable to the value ofSECURITY_COMPLIANCE_TAG, and will tag the built container images with in the associated generated manifest appropriately to support the creation of Security-Compliance Images.