Resolved issue with push job to use the image config string to determine what repo to push to for docker and harbor per image #211
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
…ine what repo to push to for docker and harbor per image
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 change to the push job will allow the push job to determine what repo (development, testing, release) to push to based on the images config string. This ensures that an individual image doesn't get pushed to multiple repos for a single GHA job for that specific image.
An example config string for an image may be: el9-23-development-True-False
In this case the push job will push to the development repo for both docker and harbor, previously it would have pushed to all three repos development, testing, and release for both docker and harbor.