Skip to content

Null-out Android env for non-Android macos builds#904

Closed
ted-xie wants to merge 1 commit into
buchgr:masterfrom
ted-xie:no_macos_android
Closed

Null-out Android env for non-Android macos builds#904
ted-xie wants to merge 1 commit into
buchgr:masterfrom
ted-xie:no_macos_android

Conversation

@ted-xie

@ted-xie ted-xie commented Jun 16, 2026

Copy link
Copy Markdown

The Intel macos deployment in BazelCI does not have the latest Android build tools installed. By default, BazelCI adds ANDROID* environment variables to builds, which registers an Android toolchain for any transitively-loaded Android deps, which causes a repo rule-level error.

To prevent this, this PR nulls out the ANDROID* environment variables.

The Intel `macos` deployment in BazelCI does not have the latest Android
build tools installed. By default, BazelCI adds `ANDROID*` environment
variables to builds, which registers an Android toolchain for any
transitively-loaded Android deps, which causes a repo rule-level error.

To prevent this, this PR nulls out the `ANDROID*` environment variables.
@ted-xie

ted-xie commented Jun 16, 2026

Copy link
Copy Markdown
Author

NOTE: An alternative is to change the BazelCI platform from macos to macos_arm64.

@mostynb

mostynb commented Jun 16, 2026

Copy link
Copy Markdown
Collaborator

I can't see any BazelCI errors in the auto-triggered CI jobs on the tip of the master branch.

But switching from macos to macos_arm64 sounds like something we should do anyway.

mostynb added a commit that referenced this pull request Jun 18, 2026
@mostynb

mostynb commented Jun 18, 2026

Copy link
Copy Markdown
Collaborator

@ted-xie: I switched to macos_arm64 instead in #905.

@mostynb mostynb closed this Jun 18, 2026
@ted-xie

ted-xie commented Jun 18, 2026

Copy link
Copy Markdown
Author

Thanks! To answer your previous question, we have an upcoming change in Bazel that would eventually cause macos build errors: https://buildkite.com/bazel/bazel-at-head-plus-downstream/builds/5546#019ecd05-779d-4897-a07e-ea1c23d102c8

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.

2 participants