[CI] Flip pulse-frontend deploys to Woodpecker - #128
Merged
Merged
Conversation
Switch push.yml from shadow tags to production tags (sha-<7> + latest) with per-branch registry cache_to, and add deploy.yml covering Nomad deploy (main + staging) and the main-only CDN scripts publish step (SRI hash + Exoscale S3 upload + Bunny purge for js.ciphera.net). Remove the GitHub Actions build-and-push workflow it replaces.
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.
Summary
pulse-frontend's real deploy pipeline from GitHub Actions to Woodpecker, following the already-soaked shadow build/push config.push.yml: production tags (sha-<7>+latest) replacing shadow tags, plus per-branchcache_tofor registry build-cache writes.deploy.yml: Nomad deploy formain(jobpulse-frontend) andstaging(jobpulse-frontend-staging), plus a main-onlycdn-scriptsstep (failure: ignore) that reproduces the GH pipeline's SRI hash + Exoscale S3 upload + Bunny purge forjs.ciphera.nettracking scripts.Changes
.woodpecker/push.yml: shadow tags →sha-${CI_COMMIT_SHA:0:7}+latest; addedcache_to: type=registry,ref=...:buildcache,mode=maxper branch image..woodpecker/deploy.yml(new):deploy/deploy-stagingsteps (digest resolve via registry manifest HEAD, jq patch ofMeta.deploy_sha+ task image +force_pull, POST to Nomad at10.10.0.110:4646) mirroring the help-frontend/website shape;cdn-scriptsstep reads the three tracking scripts from the checkout'spublic/dir (same source as the GH workflow), computes SRI, uploads tos3://ciphera-scripts/via Exoscale, purges each path on Bunny..github/workflows/build-and-push.yml(superseded)..github/workflows/test.ymluntouched.Test Plan
build(dry-run) andpushsteps go green on maindeploystep resolves the correct digest and patches Nomad jobpulse-frontend; alloc becomes healthycdn-scriptsstep uploads scripts and purges Bunny;js.ciphera.net/script.jsETag/last-modified changespulse.ciphera.net/continues to return 200 post-deploy