Build Go SDK e2e example bundle natively in CI#69909
Draft
jason810496 wants to merge 1 commit into
Draft
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.
Why
The
go_sdke2e test mode always builds its example bundle inside an ephemeralgolang:1.25-alpinecontainer, even in CI where that costs a toolchain-image pull per run. #69794 already moved thejava_sdke2e mode to a native host-toolchain build behindLANG_SDK_NATIVE_TOOLCHAIN, the same switch the breeze lang-SDK k8s job uses for its native Go build.What
_setup_go_sdk_integrationin the e2e conftest now branches onLANG_SDK_NATIVE_TOOLCHAIN: native mode runs the hostgo tool airflow-go-packdirectly (mirroring the breeze k8s lang-SDK build), while the containerized build stays the default for local runs so a dev host needs no Go installed.LANG_SDK_NATIVE_TOOLCHAINis now set totruefor thego_sdke2e mode as well.Was generative AI tooling used to co-author this PR?