Modifies republish workflow to also change versions #459
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
- Checking for new versions will now look at the current repo's source code and pick the latest tag. This is the potential new target version. It'll check the target image to see if the potential new target version exists on that image. If it does, then the job completes as the image already exists. If it does not exist, then this becomes the new target version. - A new source version is then selected. It does this by pulling the tags for the source image, sorting and picking the most recent version. This results in getting the most recent snapshot of the source image at the time the new target image is published. - The workflow then uses the updated tool for republishing an image to change both the image id and version. Signed-off-by: Daniel Mikusa <dmikusa@vmware.com>
dmikusa
added
type:enhancement
dmikusa
added
semver:minor
This was referenced Nov 11, 2021
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.
Checking for new versions will now look at the current repo's source code and pick the latest tag. This is the potential new target version. It'll check the target image to see if the potential new target version exists on that image. If it does, then the job completes as the image already exists. If it does not exist, then this becomes the new target version.
A new source version is then selected. It does this by pulling the tags for the source image, sorting and picking the most recent version. This results in getting the most recent snapshot of the source image at the time the new target image is published.
The workflow then uses the updated tool for republishing an image to change both the image id and version.
Signed-off-by: Daniel Mikusa dmikusa@vmware.com
Summary
Use Cases
Checklist