ci: remove the Buildkite CDN release pipeline - #1391
Conversation
Reverses #1382. CDN release is moving to a GitHub Actions-based deploy instead - the Twilio Buildkite pipeline, its trigger step in publish.yml, and the now-broken legacy CI badge are all removed. No replacement deploy step is added here; that's separate follow-up work.
Follow-up to the previous commit - removes publish.yml's Buildkite API trigger step, updates the dead Segment Buildkite CI badge in README.md to point at the GHA ci.yml workflow instead, and fixes a stale "(Buildkite)" doc reference in RELEASING.md that predates this migration.
✅ TVS Validation PassedShow detailsAll validation checks have successfully completed. |
|
Codecov Report✅ All modified and coverable lines are covered by tests. Please upload reports for the commit 0b04759 to get more accurate results. Additional details and impacted files@@ Coverage Diff @@
## master #1391 +/- ##
=======================================
Coverage 91.59% 91.59%
=======================================
Files 127 127
Lines 4142 4142
Branches 1033 1033
=======================================
Hits 3794 3794
Misses 348 348
☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Summary
Reverses #1382. CDN release is moving to a GitHub Actions-based deploy instead of Twilio Buildkite.
.buildkite/pipeline.ymlpublish.yml's "Trigger CDN release build" step (Buildkite API call +BUILDKITE_API_TOKEN)README.mdto point at the GHAci.ymlworkflow(Buildkite)reference inRELEASING.mdleft over from before the CI migrationNo replacement GHA-based S3 deploy step is added here - that's separate follow-up work.
Test plan
publish.ymlstill runs end-to-end (npm publish path is unaffected by this change)