ci: fix some issues for the release pipeline #493
Conversation
|
Backports to the stable branch are to be avoided unless absolutely necessary for fixing bugs, security issues, and perf regressions. Changes intended for backport should be structured such that a minimum effective diff can be committed separately from any refactoring, plumbing, cleanup, etc that are not strictly necessary to achieve the goal. Any of the latter should go only into master and ride the normal stabilization schedule. |
|
Backports to the beta branch are to be avoided unless absolutely necessary for fixing bugs, security issues, and perf regressions. Changes intended for backport should be structured such that a minimum effective diff can be committed separately from any refactoring, plumbing, cleanup, etc that are not strictly necessary to achieve the goal. Any of the latter should go only into master and ride the normal stabilization schedule. Exceptions include CI/metrics changes, CLI improvements and documentation updates on a case by case basis. |
* add TRIGGERED_BUILDKITE_TAG to the pipeline * publish a pre-release for the release id (cherry picked from commit b1e1799)
* add TRIGGERED_BUILDKITE_TAG to the pipeline * publish a pre-release for the release id (cherry picked from commit b1e1799)
#498) ci: fix some issues for the release pipeline (#493) * add TRIGGERED_BUILDKITE_TAG to the pipeline * publish a pre-release for the release id (cherry picked from commit b1e1799) Co-authored-by: Yihau Chen <[email protected]>
#499) ci: fix some issues for the release pipeline (#493) * add TRIGGERED_BUILDKITE_TAG to the pipeline * publish a pre-release for the release id (cherry picked from commit b1e1799) Co-authored-by: Yihau Chen <[email protected]>
…-xyz#493) (anza-xyz#499) ci: fix some issues for the release pipeline (anza-xyz#493) * add TRIGGERED_BUILDKITE_TAG to the pipeline * publish a pre-release for the release id (cherry picked from commit b1e1799) Co-authored-by: Yihau Chen <[email protected]>
Summary of Changes