nsaspy/a0-symbolics
1
1
Fork 0
Code Issues 140 Pull requests 7 Projects Releases Packages Wiki Activity Actions 1

ci(android): fetch setup-android and setup-gradle by full URL #97

Merged
nsaspy merged 5 commits from fix/ci-missing-actions into main 2026-09-06 11:55:20 +00:00
Conversation 0 Commits 5 Files changed 3 +6 -5
nsaspy commented 2026-09-05 04:37:44 +00:00
Owner
Copy link

What changed

Every Android CI run (including #88) fails during action resolution, before any step executes:

unable to clone 'https://data.forgejo.org/android-actions/setup-android' ... remote: Not found.

The Forgejo action mirror at data.forgejo.org does not mirror android-actions/setup-android or gradle/actions/setup-gradle (verified: git ls-remote https://data.forgejo.org/<owner>/<repo> returns "remote: Not found." for both, while actions/checkout, actions/setup-java, actions/upload-artifact and the docker/* actions resolve fine).

Forgejo supports fully-qualified action URLs, so this PR references both actions by their https://github.com/... URLs. No workflow logic changes.

Why a PR to main

pull_request workflows run the workflow file from the PR merge ref, so fixing android.yml on main unbreaks CI for all open Android PRs (#88 and others) that do not modify the workflow themselves.

Verification

This PR's own CI self-tests the change: the paths filter triggers Android APK and the merge ref now contains the fixed workflow. First-ever real run of gradle testDebugUnitTest lintDebug assembleDebug in CI.

Related: #88

## What changed Every Android CI run (including #88) fails during action resolution, before any step executes: > unable to clone 'https://data.forgejo.org/android-actions/setup-android' ... remote: Not found. The Forgejo action mirror at data.forgejo.org does not mirror `android-actions/setup-android` or `gradle/actions/setup-gradle` (verified: `git ls-remote https://data.forgejo.org/<owner>/<repo>` returns "remote: Not found." for both, while `actions/checkout`, `actions/setup-java`, `actions/upload-artifact` and the `docker/*` actions resolve fine). Forgejo supports fully-qualified action URLs, so this PR references both actions by their `https://github.com/...` URLs. No workflow logic changes. ## Why a PR to main `pull_request` workflows run the workflow file from the PR merge ref, so fixing `android.yml` on main unbreaks CI for all open Android PRs (#88 and others) that do not modify the workflow themselves. ## Verification This PR's own CI self-tests the change: the paths filter triggers `Android APK` and the merge ref now contains the fixed workflow. First-ever real run of `gradle testDebugUnitTest lintDebug assembleDebug` in CI. Related: #88
ci(android): fetch setup-android and setup-gradle by full URL
Some checks failed
Android APK / build (pull_request) Failing after 24m4s
Details
244099b205 
The Forgejo action mirror at data.forgejo.org does not mirror
android-actions/setup-android or gradle/actions/setup-gradle, so every
Android workflow fails during action resolution before any step runs.
Reference both actions with fully-qualified URLs, which Forgejo
supports, so the runner clones them directly from github.com.
ci(android): treat artifact upload as best-effort
Some checks failed
Android APK / build (pull_request) Has been cancelled
Details
a18f3cbb0c 
This Forgejo instance does not implement the upload-artifact@v4
artifact service, so the upload step always fails after a successful
build. Keep the gradle gate authoritative and make the upload
non-blocking.
ci: fetch github-script by full URL
All checks were successful
Android APK / build (pull_request) Successful in 27m21s
Details
9eb2462a3b 
actions/github-script is not mirrored on data.forgejo.org; docker
release resolution and the (inert) close-inactive job reference it by
short ref. Use the fully-qualified URL like the other unmirrored
actions.
Merge branch 'main' into fix/ci-missing-actions
All checks were successful
Android APK / build (pull_request) Successful in 27m17s
Details
ea396662ed
ci(android): allow 45 minutes for the SDK and gradle build
All checks were successful
Android APK / build (pull_request) Successful in 24m43s
Details
f81ed6270b 
The build takes about 22 minutes on a quiet runner; concurrent nix
closures on the shared runner pushed a run past the 30-minute ceiling.
Raise the job timeout to keep the gate meaningful under contention.
nsaspy merged commit 91c1569fa8 into main 2026-09-06 11:55:20 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
accessibility
Barrier affecting people with disabilities

  
bug
Something isn't working

  
documentation
Improvements or additions to documentation

  
duplicate
This issue or pull request already exists

  
enhancement
New feature or request

  
good first issue
Good for newcomers

  
help wanted
Extra attention is needed

  
invalid
This doesn't seem right

  
question
Further information is requested

  
wontfix
This will not be worked on

No labels
accessibility
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nsaspy/a0-symbolics!97
No description provided.