v1.17: ci: add release pipeline (backport of #466) #486
Conversation
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.
Problem
we should have an automatic release pipeline. this PR is the first step. it will be triggered by a pushing tag. when it becomes stable, I will push another PR for pushing tag weekly!
Summary of Changes
add 3 different jobs in this release pipeline
trigger-buildkite-pipeline
this one will trigger secondary pipeline on buildkite instead of webhook. It will ensure all secondary pipelines are executed successfully.
image
draft-release
create a draft release for binaries.
image
version-bump
create a version bump PR automatically.
image
Before Merge
TRIGGER_BK_BUILD_TOKENto Github ActionsThis is an automatic backport of pull request ci: add release pipeline #466 done by Mergify.