RUM-4079 chore: Migrate E2E Tests app workflow to GitLab #1957
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.
What and why?
π¦ π§° This PR migrates E2E Tests workflow to GitLab (build β sign β upload to synthetics). It follows other GitLab migration efforts: #1953, #1945, #1921 and #1910.
The only remaining automation in Bitrise is β Dogfooding. It will be migrated next.
How?
This work is leveraging existing
code-sign.sh
flow. Previous script was renamed and modularized with enhanced errors handling. It now creates all code-signing files (certificate, provisioning profile, and xcconfig) from CI secrets and delegatesarchive
,export
andupload
routines toE2ETests/Makefile
as before.π Extra elements:
Runner.ipa
is also deployed as CI job artifact (stored for short retention)DRY_RUN
env is supported for local development and testing (does all but the s8s upload)Review checklist
Custom CI job configuration (optional)