Secrets are never exposed to pull_request runs from forks, so checkEnv.js
throws on MAESTRO_PASSWORD after a full APK build and emulator boot, and the
red check is indistinguishable from a real test failure. The existing guard
checked github.event.pull_request.fork, a field that does not exist on the
pull_request payload (it lives at head.repo.fork), so it was always true.
Gate both jobs at job level on head.repo.full_name == github.repository
(workflow_dispatch still runs), and drop the dead step-level condition.
Fixes#7653
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
With the default (queue: single), a run that finishes Build APK while
another run is already pending in the maestro-test group cancels that
pending run, which then never gets a Maestro verdict for its commit.
queue: max keeps the one-at-a-time constraint (no cancel-in-progress) and
lets up to 100 runs wait, at no runner cost.
Fixes#7654
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* Add free disk space action
* Remove 'upload APK for Maestro' step since it's no longer used
* Re-enable tool-cache removal
* Add the free disk space step to other gradle-related jobs
* Use commit SHA
* Disable removing `large-packages`
* Increase the timeout for asserting 'Be in your element' is visible
* Disable the chrome onboarding flow. This simplifies the code a lot and helps avoid corner cases.
* More delays with timeout!
* Add more info to the summary, specially when the tests fail, so we can quickly check what failed.
* Make sure Maestro tests can't run in parallel, but APK builds can
* Ensure the CI is marked as failed when Maestro test is failing
* Fix typo in String to disable bookmark in ChromeCustomTab
* Fix Maestro test now that matrix.org is using MAS to authenticate.
* Fix Maestro test - other issues due to recent changes.
* Maestro: add test on Element Call
* Run through Chrome on boarding step.
* Try suggestion from https://github.com/mobile-dev-inc/Maestro/issues/1126#issuecomment-2842220361
* Revert "Try suggestion from https://github.com/mobile-dev-inc/Maestro/issues/1126#issuecomment-2842220361"
This reverts commit d400644622c1a240deb61040f9095e3221e07f21.
* Add comment on Maestro flow.
- Remove the `workflow_run` configuration for the Maestro job.
- Make the 'build apk' job always run again too.
- Make sure the test results are uploaded when the Maestro job fails too (this broke somehow).
Add Maestro local CI workflow:
- Remove previous Maestro Cloud.
- Use an emulator with Pixel 7 Pro - API 35.
- Allow to record several videos in the background to verify the run.
- Upload test results.
- Allow either dispatching a new flow, running the 'build apk' job or run with a PR after the 'Build APK' flow has succeeded.
renovate[bot]
Benoit Marty
andreBurnt
Benoit Marty
Jorge Martin Espinosa