AUT-271: make separate tags and docker images pushes for production deploys of autograph-edge #332
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
…eploys of autograph-edge This change gives us separate tags for prereleases and releases, which will allow our deployment pipeline to separate out stage & production deploys. I've also adjusted the `latest` tag to only be used on pushes to main, rather than all deployments. This will ensure that any ongoing dev work against main won't be disrupted if we cut a release. Here's some example runs in my own repo (they fail, but the important part is the metadata step): * [A push to main](https://github.com/bhearsum/autograph-edge/actions/runs/11298955041/job/31428961407), which just generates a `latest` tag * [Publishing the `1.1.1` prerelease](https://github.com/bhearsum/autograph-edge/actions/runs/11298968687/job/31428998722) just generates a `1.1.1-prerelease` tag * [Republishing `1.1.1` as a full release](https://github.com/bhearsum/autograph-edge/actions/runs/11298988470/job/31429054717) just generates a `1.1.1` tag
|
d'oh, forgot i can't open PRs from a fork here and have tests run. closing to re-open from the main repo. |
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 gives us separate tags for prereleases and releases, which will allow our deployment pipeline to separate out stage & production deploys.
I've also adjusted the
latesttag to only be used on pushes to main, rather than all deployments. This will ensure that any ongoing dev work against main won't be disrupted if we cut a release.Here's some example runs in my own repo (they fail, but the important part is the metadata step):
latesttag1.1.1prerelease just generates a1.1.1-prereleasetag1.1.1as a full release just generates a1.1.1tag