Run android, android-asan, fenix and ios build tasks on git-backed pushes
Categories
(Firefox Build System :: Task Configuration, task)
Tracking
(Not tracked)
People
(Reporter: nhadji, Assigned: nhadji)
References
(Blocks 1 open bug)
Details
Attachments
(9 external files)
Part of the Mercurial to Git CI migration: remove run-on-repo-type: [hg] and clone-with: hg from the mobile build definition files so these builds can run on git-backed pushes: taskcluster/kinds/build/android.yml, android-asan.yml, fenix.yml, ios.yml.
Verified with the two-push workflow before submission:
- Baseline try (hg), guards in place: https://treeherder.mozilla.org/jobs?repo=try&revision=ea91708a6812bd945887b06f0bfd46abb8e4ef1d - all green (the only red,
build-android-geckoview-docs/opt, is pre-existing on both backends and belongs toandroid-stuff.yml, excluded from this batch). - staging-firefox (git), guards removed: https://treeherder.mozilla.org/jobs?repo=staging-firefox&revision=8c838ef54073e24217af181c4fa230e3c4ab0e4d and completion push https://treeherder.mozilla.org/jobs?repo=staging-firefox&revision=2b7303ec04ebf7d46be3d44d056fcbffc78df459 - all android/ios builds green,
run-task-gitclone from github.com confirmed, artifact parity verified (expected deltas only: maven coordinates embed the repo name; shippable builds omit crashreporter-symbols-full becauseupload-symbolsvariants are project-gated off staging-firefox).
Notes: build-android-x86_64-ccov/opt was excluded from the git verification (code-coverage-artifacts requires the project.codecoverage.v1.tasks_done route, not granted on git repos yet); android-stuff.yml is deferred to its own bug (pre-existing bustage on both backends).
| Assignee | ||
Comment 1•1 month ago
|
||
Updated•1 month ago
|
| Assignee | ||
Comment 2•1 month ago
|
||
| Assignee | ||
Comment 3•1 month ago
|
||
| Assignee | ||
Comment 4•1 month ago
|
||
| Assignee | ||
Comment 5•1 month ago
|
||
Part of the Mercurial -> Git CI migration: remove the hg-only guards from
the build/android-stuff kind.
build-android-geckoview-docs cannot be fully verified at level 1 on either
backend: after building the javadoc it uploads it to mozilla/geckoview
(gh-pages) with a deploy key held in the level-3 secret
project/releng/gecko/build/level-3/geckoview-docs-upload, so try and
staging runs fail at that upload step whatever the VCS. What is verifiable
matches: on a git-backed push (staging-firefox) the task is scheduled, clones
with git, builds the javadoc (BUILD SUCCESSFUL) and fails at the same upload
step as the hg try baseline (lando 93250). On mozilla-central (level 3) the
task is green.
| Assignee | ||
Comment 6•1 month ago
|
||
Remove the run-on-repo-type: [hg] guard so signing-apk tasks are
scheduled on git-backed pushes, together with the android build family.
Dep-signing on git-backed pushes needed the Chain of Trust fix from bug
2070846 (scriptworker 63.6.1, deployed 2026-10-08). Verified on a
git-backed push (staging-firefox 3f1d4444b983, task group
RA6yNPC9RaSiJSRzem7qZw): all 5 signing-apk tasks completed (fenix debug,
nightly, nightly-simulation; focus debug, nightly).
Landing waits on https://github.com/mozilla/global-platform-admin/pull/7642
(GitHub app install for the repo).
| Assignee | ||
Comment 7•1 month ago
|
||
Remove the run-on-repo-type: [hg] guard so signing-bundle tasks are
scheduled on git-backed pushes, together with the android build family.
Dep-signing on git-backed pushes needed the Chain of Trust fix from bug
2070846 (scriptworker 63.6.1, deployed 2026-10-08). Verified on a
git-backed push (staging-firefox 3f1d4444b983, task group
RA6yNPC9RaSiJSRzem7qZw): all 4 signing-bundle tasks completed (fenix
debug, nightly; focus debug, nightly).
Landing waits on https://github.com/mozilla/global-platform-admin/pull/7642
(GitHub app install for the repo).
| Assignee | ||
Comment 8•1 month ago
|
||
build-apk, build-bundle, build-extensions, build-fat-aar and
build-samples-browser carry run-on-repo-type: [hg] and clone-with: hg,
so no Fenix, Focus or GeckoView app build is scheduled on a git-backed push.
With the guards gone these tasks are scheduled there and clone from GitHub.
Verified on Sep 21: an 18-task sample was green on both an hg try push
(lando 94775, push 2043059) and a staging-firefox git push (5aa6b5d75cae),
86/86 tasks of the git graph completed, and the artifacts matched apart from
the repository name in the maven coordinates. The diff was re-applied on
current main; the graph still generates on git with the same task counts.
Landing waits on a capacity go from ahal: this adds about 178 tasks to each
git-backed push. It also waits on
https://github.com/mozilla/global-platform-admin/pull/7642 (GitHub app
install for the repo).
Comment 10•1 month ago
|
||
| bugherder | ||
Updated•1 month ago
|
Comment 11•20 days ago
|
||
Comment 12•20 days ago
|
||
| bugherder | ||
Comment 13•16 days ago
|
||
Comment 14•16 days ago
|
||
Comment 15•16 days ago
|
||
| bugherder | ||
Comment 16•10 days ago
|
||
| Assignee | ||
Comment 17•10 days ago
|
||
Drop run-on-repo-type: [hg] and clone-with: hg from instrumented-build-apk,
generate-baseline-profile-firebase, instrumented-build-macrobenchmark-apk,
run-macrobenchmark-firebase and ui-test-apk, so these Fenix tasks schedule on
git-backed pushes and check out the GitHub mirror (run-task-git, shallow
clone).
Verified on try with the whole chain cloning from Git, all green:
instrumented-build-apk-fenix, generate-baseline-profile-firebase-fenix,
instrumented-build-macrobenchmark-apk-fenix, run-macrobenchmark-firebase-fenix
and the ui-test-apk-fenix-arm-debug-smoke run, including the two tasks that
talk to Firebase Test Lab.
https://treeherder.mozilla.org/jobs?repo=try&revision=c2b24335f065e2d63c7fa56eebf2d0f7375c3f97
The Fenix baseline profile task and the four ui-test-apk tasks without a
run-on-projects ran on every project through the implicit default; on a
Git-backed repository that default also covers enterprise-firefox, which
has no Fenix. They now spell out [trunk, release]: the same projects as
before on Mercurial, the release branches of the firefox repository on
Git, and not enterprise-firefox. Checked with the enterprise, central,
autoland and beta parameter sets: their target task sets are unchanged by
this patch.
Comment 18•10 days ago
|
||
| bugherder | ||
Comment 19•5 days ago
|
||
Comment 20•5 days ago
|
||
| bugherder | ||
Updated•1 day ago
|
Updated•1 day ago
|
Updated•1 day ago
|
Description
•