ci: retire Docker build/push, publishing moved to postguard - #206
Merged
Conversation
encryption4all/postguard's own delivery pipeline now builds and pushes ghcr.io/encryption4all/cryptify (postguard#293, PR #309, verified against merge commit 506144c: build-cryptify/scan-cryptify/ finalize-cryptify all succeeded and pushed the :edge tag). Keeping both pipelines live would race on the same tags. release-plz's release/changelog-PR jobs are untouched here — out of scope for this ticket.
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
1 participant
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.
Summary
buildandfinalizejobs (the Docker build/push pipeline) from this repo'sci.yml.ghcr.io/encryption4all/cryptifyhas moved toencryption4all/postguard's owndelivery.yml, which builds this crate as a workspace member. Verified working against merge commit506144c:build-cryptify/scan-cryptify/finalize-cryptifyall succeeded and pushed the:edgetag (postguard#293, postguard#309).parse-release/version/releases_createdoutput plumbing inrelease-plz-release, whose only consumer was the removedfinalizejob.qualityandrelease-plz-pr/release-plz-releaseare untouched — out of scope for this ticket.Part of postguard#293 (step 4 of its checklist). This is the step that stops two pipelines racing on the same GHCR tags — hold off merging until you've had a chance to look at the diff, since it removes this repo's only remaining Docker publish path.