-
Notifications
You must be signed in to change notification settings - Fork 174
ci: update Buildkite pipeline for GitHub CLI migration #2602
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -468,10 +468,13 @@ steps: | |
| echo "+++ Installing required packages" | ||
| sudo apt -y update && sudo apt -y install devscripts pandoc reprepro | ||
|
|
||
| echo "+++ Downloading github-release" | ||
| curl -L https://mirror.bazel.build/github.com/c4milo/github-release/releases/download/v1.1.0/github-release_v1.1.0_linux_amd64.tar.gz | sudo tar xz -C /usr/local/bin | ||
| sudo chown root:root /usr/local/bin/github-release | ||
| sudo chmod 0755 /usr/local/bin/github-release | ||
| echo "+++ Installing GitHub CLI" | ||
| mkdir -p -m 755 /etc/apt/keyrings | ||
| wget -qO- https://cli.github.com/packages/githubcli-archive-keyring.gpg | sudo tee /etc/apt/keyrings/githubcli-archive-keyring.gpg > /dev/null | ||
| sudo chmod go+r /etc/apt/keyrings/githubcli-archive-keyring.gpg | ||
| echo "deb [arch=\$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/githubcli-archive-keyring.gpg] https://cli.github.com/packages stable main" | sudo tee /etc/apt/sources.list.d/github-cli.list > /dev/null | ||
| sudo apt -y update | ||
| sudo apt -y install gh | ||
|
|
||
| echo "+++ Checking out Git branch" | ||
| git fetch origin ${BUILDKITE_BRANCH} | ||
|
|
@@ -489,6 +492,7 @@ steps: | |
| rm -f "\${keyfile}" | ||
|
|
||
| echo "+++ Deploying release" | ||
| sed -i '/rm -f.*sha256/,/done/d' scripts/ci/build.sh | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Why this? Should we just fix the code in the bazel repo?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Its a safer step to remove the signing loop. Also, this command does nothing if the signing loop wasn't already present. essentially github CLI can handle auth, signing, and artifact checks. But i just left it as is, so that i dont break any for now. |
||
| source scripts/ci/build.sh | ||
| deploy_release "\${ARTIFACTS}" | ||
|
|
||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we can actually delete bazel-release-arm64.yml
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The corresponding CI job is already gone.