[CI] Add Woodpecker shadow pipeline (build + push, dry-run) - #127
Merged
Merged
Conversation
Shadow-only dry_run build + push steps mirroring the existing GitHub Actions workflow's branch routing (main -> pulse-frontend, staging -> pulse-frontend-staging) and Vault-sourced Next.js build args. No deploy step yet; GitHub Actions remains the deploying pipeline during shadow.
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
.woodpecker/build.ymland.woodpecker/push.ymlfor the Woodpecker CI shadow phase, running alongside the existing GitHub Actions workflow (unchanged).build-and-push.yml's branch routing:main->ciphera-net/pulse-frontend,staging->ciphera-net/pulse-frontend-staging, each with its own Vault-sourcedNEXT_PUBLIC_*build args (namespaced per-branch as Woodpecker repo secrets).build.ymlrunsdry_run: truewithshadow-<sha7>/shadow-staging-<sha7>tags;push.ymldepends onbuildand pushes the same shadow tags to the registry for verification.deploy.ymlyet, and no Nomad job changes — this phase only proves out build/push in Woodpecker. Deploy + main-only extras (SRI hashing, Exoscale script upload, Bunny purge) land in a later flip phase.Changes
.woodpecker/build.yml:write-npmrcstep (orgnpm_tokensecret) + branch-gatedbuild/build-stagingstep pair usingplugin-docker-buildx:6.1.1..woodpecker/push.yml: same npmrc + branch-gatedpush/push-stagingstep pair,depends_on: [build].Test Plan
build+pushrun dry-run/push successfully onmainstagingand confirmbuild-staging+push-stagingrun successfullymain, 1 green run onstaging