Skip to content

[CI] Remove buildkite from metrics container #143049

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

Merged

Conversation

boomanaiden154
Copy link
Contributor

Now that buildkite has been sunsetted, remove buildkite tracking from the metrics container as it does not do anything.

Now that buildkite has been sunsetted, remove buildkite tracking from
the metrics container as it does not do anything.
boomanaiden154 added a commit to boomanaiden154/llvm-zorg that referenced this pull request Jun 6, 2025
Now that buildkite has been sunsetted, we no longer need to keep track of
the Buildkite workflows. llvm/llvm-project#143049 does
this on the metrics container side. This patch adjusts the deployment to
those changes. Note that patch needs to land first before this can be
applied.
@boomanaiden154
Copy link
Contributor Author

If someone could run the following commands to ensure the container gets restarted, that would be great:

gcloud container clusters get-credentials llvm-premerge-cluster-us-central --location us-central1-a
kubectl get pods -n metrics # copy and paste the pod name
kubectl delete pod <metrics pod name> -n metrics

@boomanaiden154 boomanaiden154 merged commit 34e5d8e into llvm:main Jun 6, 2025
10 checks passed
@boomanaiden154 boomanaiden154 deleted the remove-buildkite-metrics-container branch June 6, 2025 19:58
@cmtice
Copy link
Contributor

cmtice commented Jun 7, 2025

If someone could run the following commands to ensure the container gets restarted, that would be great:

gcloud container clusters get-credentials llvm-premerge-cluster-us-central --location us-central1-a
kubectl get pods -n metrics # copy and paste the pod name
kubectl delete pod <metrics pod name> -n metrics

Have these been run by anybody else, or do they still need to be run?

@boomanaiden154
Copy link
Contributor Author

Have these been run by anybody else, or do they still need to be run?

Not sure. It doesn't hurt to run them twice though. You can tell by seeing how long the pod has been up. It was ten days ago yesterday.

boomanaiden154 added a commit to llvm/llvm-zorg that referenced this pull request Jun 7, 2025
Now that buildkite has been sunsetted, we no longer need to keep track
of the Buildkite workflows.
llvm/llvm-project#143049 does this on the
metrics container side. This patch adjusts the deployment to those
changes. Note that patch needs to land first before this can be applied.
@cmtice
Copy link
Contributor

cmtice commented Jun 7, 2025

Have these been run by anybody else, or do they still need to be run?

Not sure. It doesn't hurt to run them twice though. You can tell by seeing how long the pod has been up. It was ten days ago yesterday.

Done. :-)

rorth pushed a commit to rorth/llvm-project that referenced this pull request Jun 11, 2025
Now that buildkite has been sunsetted, remove buildkite tracking from
the metrics container as it does not do anything.
DhruvSrivastavaX pushed a commit to DhruvSrivastavaX/lldb-for-aix that referenced this pull request Jun 12, 2025
Now that buildkite has been sunsetted, remove buildkite tracking from
the metrics container as it does not do anything.
tomtor pushed a commit to tomtor/llvm-project that referenced this pull request Jun 14, 2025
Now that buildkite has been sunsetted, remove buildkite tracking from
the metrics container as it does not do anything.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants