Skip to content
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

Tag build images with teleport8 instead of go version #10211

Merged
merged 2 commits into from
Feb 8, 2022

Conversation

tcsc
Copy link
Contributor

@tcsc tcsc commented Feb 8, 2022

Prior to this patch, the buildbox images used for CI have always just been tagged with the version of Go they support. In the past this has been discrete enough to stay inside individual release boundaries.

Recently, though, the version of Go used by Teleport 8 and Teleport 9 has remained constant, while other requirements of the the build environment have changed, leading to the unfortunate situation where publishing a buildbox image that works for Teleport 9 breaks the Teleport 8 build.

This patch de-couples the version of the buildbox from the version of Go installed on it, and produces a new teleport8-tagged buildbox image for Teleport 8 builds to use.

@tcsc tcsc requested a review from zmb3 February 8, 2022 01:27
@tcsc tcsc requested review from webvictim and russjones February 8, 2022 01:27
@@ -4721,6 +4721,7 @@ name: build-buildboxes
environment:
GID: "1000"
RUNTIME: go1.17.3
BUILDBOX_VERSION: teleport8
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is the idea here that once this is backported we will then update master to something other than teleport8?

Copy link
Contributor Author

@tcsc tcsc Feb 8, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR is targeted at branch/v8, and I've added branch/v8 to the trigger selection on the Drone pipeline, so that Drone will build the images on merges to branch/v8 as well as master. master should be untouched.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can forward-port it to master with teleport9 if that makes sense, but I was mainly focussed on unjamming v8

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