Migrate Agent Pipeline to Agent Cluster #3018
Merged
Conversation
This file contains 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
Internally at Buildkite we're refactoring our clusters and will be moving the agent pipeline to a new cluster. This PR makes the queue names override-able to allow running the pipeline in both the previous and new cluster.
This was referenced Oct 8, 2024
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.
Description
Internally at Buildkite we're refactoring our clusters and will be moving the agent pipeline to a new cluster. This PR makes the queue names override-able to allow running the pipeline in both the previous and new cluster.
Context
https://3.basecamp.com/3453178/buckets/1933834/messages/7835428487
Changes
Queues can be overridden using environment variables from the Pipeline Steps configuration. This allows running the agent pipeline simultaneously in the Agent and existing cluster.
Assumes an OIDC role to publish docker images to internal registry.
Testing
Successful builds in both the current and new cluster.