Repository navigation
docker.yml: manual run can rebuild and archive an existing release tag - #44
Merged
Merged
Conversation
When a release's Zenodo image upload fails there was no correct way to retry: a manual run built main, labelled the image 'latest' and, if the upload succeeded, published a permanent Zenodo record with version 'latest'. Re-creating the release would mint a new source DOI. workflow_dispatch now takes an optional 'tag'. With it, the job checks out that tag, gives the image the same semver tags and Zenodo version label as the release run, and leaves 'latest' alone. Without it, behaviour is unchanged.
This file contains hidden or 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
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.
When a release's Zenodo image upload fails, there was no correct way to retry it:
workflow_dispatch) builtmain, labelled the imagelatest, and — if the upload succeeded — published a permanent Zenodo record with versionlatest;This adds an optional
taginput to the manual trigger. Withtag: v0.1.0the job:v0.1.0;0.1.0/0.1/sha-…exactly as the release run would;latestback to the old release;v0.1.0.Without the input, behaviour is unchanged. Release runs are unchanged.
Checked: YAML parses,
actionlintclean, template tests pass. First use: retrying the failed image upload ofannefou/logrono-vulnerable-room-to-greenv0.1.0 (together with #43, so a failure will now say why).