Skip to content

ci: install Ruby before running bundler on the Android deploy - #15

Merged
nathanfallet merged 1 commit into
mainfrom
ci/setup-ruby-on-android
Aug 1, 2026
Merged

nathanfallet merged 1 commit into
mainfrom
ci/setup-ruby-on-android

Conversation

@nathanfallet

Copy link
Copy Markdown
Member

deploy-android has never succeeded, on any run. It does cd androidApp && bundle install on
ubuntu-latest, whose image ships no Ruby, so it dies on bundle: command not found — including
on the June 2025 run where iOS did go through.

The job was written for a self-hosted runner. The file still carries the evidence:

runs-on: ubuntu-latest #[ self-hosted, unix ]

latexcards-app and controlresell-app run this same fastlane setup on
guimauvedigital-github-runner-* and need no Ruby step, because those machines have it.
controlresell-app even keeps the fix in the file, commented out and labelled "Only on GH hosted
runners"
. This is that block, uncommented.

3.3 is the version that comment pins, and what latexcards-app's Gemfile.lock records
(ruby 3.3.6p108).

Only Android

The iOS job fails for an unrelated reason: the key in MATCH_REPO_KEY is no longer authorized on
groupeminaste/match, which has no deploy key at all today. Its counterpart on
guimauvedigital/match — created November 2024, read-only — was last used this morning, which is
what keeps the other two apps deploying.

That is fixed outside this repository, by registering a deploy key. Keeping it out of this PR is
deliberate: after the merge, each job's outcome points at exactly one cause.

Expected after merge

  • deploy-android gets past bundle install. Whether it then uploads depends on the Play Store
    credentials, which have never been exercised — this is the first time the job will reach fastlane
    at all, so a failure past this point would be new information rather than the same old one.
  • deploy-ios passes only if the deploy key is in place.

Note the Android job also assembles only the flavor being distributed now (bundleProductionRelease
rather than bundleRelease), which came with the migration PR — otherwise it would also build the
local flavor, which exists purely to talk to a backend on a developer's machine.

`deploy-android` has never succeeded. It runs `cd androidApp && bundle install`
on `ubuntu-latest`, whose image ships no Ruby, so the step dies on
`bundle: command not found` — including on the last green-ish run back in
June 2025.

The job was written for a self-hosted runner, where Ruby is already there:
the file still carries `#[ self-hosted, unix ]` next to `runs-on`, and
latexcards-app and controlresell-app both run this same fastlane setup on
`guimauvedigital-github-runner-*` without any Ruby step. controlresell-app
even keeps the fix written down, commented out, marked "Only on GH hosted
runners".

3.3 is what that comment pins and what latexcards-app's Gemfile.lock records
(`ruby 3.3.6p108`).

Only the Android job changes. The iOS one fails for an unrelated reason — the
key in MATCH_REPO_KEY is no longer authorized on groupeminaste/match — which
is fixed outside this repository, and keeping the two apart is what makes the
next run readable.
@nathanfallet
nathanfallet merged commit 59c8fd7 into main Aug 1, 2026
1 check passed
@nathanfallet
nathanfallet deleted the ci/setup-ruby-on-android branch August 1, 2026 19:16
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.

1 participant