Repository navigation
Upload build artifacts write-once to jenkins-artifacts - #5
Merged
Merged
Conversation
Upload with aws s3 cp --no-overwrite and fail the step if the version folder already exists. The GitHub Actions role will require If-None-Match on jenkins-artifacts uploads. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YEpbb7PWaTRuHJfSwZyDV1
joemcbride
approved these changes
Oct 16, 2026
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
2 participants
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.
What changed
.github/workflows/build.yml, step "Upload Certbot Lambda Assets to S3": uploadscertbot/*.ziptojobs/certbot-lambda/<version>/in the us-west-2 jenkins-artifacts bucket.Uploads use
aws s3 cp --no-overwrite.The step fails before it uploads if the version folder already exists in a jenkins-artifacts bucket.
Why
DovetailSoftware/blue-operations#3173 makes the GitHub Actions AWS role write-once on jenkins-artifacts: S3 rejects an upload that would replace an existing artifact. After that change applies, an upload without
--no-overwritegets a 403.--no-overwritesendsIf-None-Match: *, which the new policy requires. But when the key already exists, the CLI skips the file and does not return an error. The check before the upload makes the step fail in that case.What to expect
::error::s3://.../<version>/ already exists. To upload again, make a new version (a new commit).🤖 Generated with Claude Code
https://claude.ai/code/session_01YEpbb7PWaTRuHJfSwZyDV1