Repository navigation
android-cloud-check: SETUP_RUBY input to skip setup-ruby on runners that ship Ruby - #124
Merged
Merged
Conversation
…hat ship Ruby android-setup-environment already has a `ruby` switch, but the reusable workflow never forwarded it, so every caller runs ruby/setup-ruby. On the self-hosted mac runners that step fails before Java is even set up: setup-ruby writes its tool cache under /Users/runner, which the runner user cannot create (EACCES), while the image already ships Ruby on PATH. SETUP_RUBY (boolean, default true) keeps today's behaviour and lets the mac callers pass false.
matejsemancik
approved these changes
Oct 7, 2026
This was referenced Oct 7, 2026
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
2 participants
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.
Summary
android-cloud-check.ymlgains an optionalSETUP_RUBYinput (boolean, defaulttrue) forwarded to therubyswitch thatandroid-setup-environmentalready has. Default keeps today's behaviour. Mac callers passfalse.Why
With
RUNS_ON: self-hosted(2.5.0, #121) the job dies in "Set up environment" before Java is even installed:ruby/setup-rubywants its tool cache under/Users/runner, which the runner user (runnerm1) cannot create:The mac image already ships Ruby on PATH (setup-ruby even logs that it removes it from PATH), so there is nothing to install there. The shared path had not been exercised on the mac until now.
Changes
SETUP_RUBYinput, forwarded asruby: ${{ inputs.SETUP_RUBY }}.Notes
android-cloud-nightly-build.ymlonce that one moves to the mac runners.🤖 Generated with Claude Code
https://claude.ai/code/session_015tyUXzyBw4NEtGE91PcZGC