[Phase 2] Add Bitrise E2E pipeline skeleton

[kieran-osgood-shopify]

Stack Context

This is Phase 2 of the BrowserStack Maestro E2E stack for Checkout Kit, stacked on the Phase 1 matrix/smoke foundation.

Parent issue: https://github.com/shop/issues-checkout-kit/issues/1096
Epic: https://github.com/shop/issues-checkout-kit/issues/1084

What?

Adds the Bitrise E2E pipeline skeleton without real BrowserStack execution:

• e2e/bitrise.yml with an e2e graph pipeline
• split package/build/run/report workflow shape
• placeholder RN iOS and RN Android artifact workflows
• placeholder matrix-row run fanout workflow
• placeholder aggregate report workflow
• Bitrise Pipeline intermediate file sharing placeholders
• Bitrise setup docs at e2e/BITRISE.md
• count helper on the run plan CLI for E2E_BROWSERSTACK_RUN_PLAN_COUNT
• Bitrise CLI installed by dev up via dev.yml
• Shopify Bitrise compatibility defaults:
  • no activate-build-cache-for-xcode or activate-build-cache-for-gradle add-on steps
  • Ruby pinned via the Bitrise tools: directive (ruby: 3.3.6, a version pre-installed on the stack) so runs do not depend on the repo .ruby-version

Why?

We want the build/test/report topology and matrix fanout model in place before introducing real app artifacts or BrowserStack API calls.

This keeps Phase 2 focused on CI shape, artifact handoff contracts, caching placeholders, Bitrise app setup documentation, local Bitrise config validation, and compatibility with Shopify's Bitrise environment. The Bitrise config lives under e2e/ because it is scoped to the E2E pipeline.

Validation

shadowenv exec -- ruby e2e/scripts/e2e_matrix_to_browserstack_run_plan validate
shadowenv exec -- ruby e2e/scripts/e2e_matrix_to_browserstack_run_plan count
shadowenv exec -- bitrise validate -c e2e/bitrise.yml

shadowenv exec -- /opt/dev/bin/dev up installed the Bitrise CLI successfully, then failed later during workspace setup because this worktree does not have storefront .env/Swift sample generated config. bitrise version returned 2.39.2 afterwards and bitrise validate -c e2e/bitrise.yml passed.

[kieran-osgood-shopify]

• [Phase 7] Soft-launch E2E PR checks #364 : 2 dependent PRs (#401 , #417 )
• [Phase 6] Report E2E results to GitHub #363
• [Phase 5] Run BrowserStack Maestro from E2E matrix rows #362
• [Phase 4] Build React Native iOS E2E IPA artifact #361
• [Phase 3] Build React Native Android E2E APK artifact #360
• [Phase 2] Add Bitrise E2E pipeline skeleton #357 👈 (View in Graphite)
• [Phase1] Add E2E matrix launch smoke foundation #356
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[kiftio]

looks good, couple of minor docs qs.

[tiagocandido]

The PR body says this config sets RBENV_VERSION=system, but it is missing here. Since the repo has its own .ruby-version and this Bitrise config pins another Ruby version, scripts from the checkout can still ask rbenv for the checkout version before the run plan is produced.

Could we restore the app-level override?

Suggested change

	- E2E_STRICT: "false"
	- RBENV_VERSION: system
	- E2E_STRICT: "false"

[kieran-osgood-shopify]

Thanks for catching that, the PR body got stale as we're no longer using rbenv (we rely now on the tools version which uses asdf

tools:
  ruby: 3.3.6
  nodejs: 22.14.0

I have a ticket here: https://github.com/orgs/shop/projects/1142/views/1?sliceBy%5Bvalue%5D=kieran-osgood-shopify&pane=issue&itemId=4837082758&issue=shop%7Cissues-checkout-kit%7C1136 to resolve the ruby inconsistencies holistically across the repo as we currently have at least 3 .ruby-version files

[kieran-osgood-shopify]

Merge activity

• Jul 8, 3:12 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• Jul 8, 3:14 PM UTC: Graphite rebased this pull request as part of a merge.
• Jul 8, 4:40 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• Jul 8, 4:40 PM UTC: @kieran-osgood-shopify merged this pull request with Graphite.

[tiagocandido]

Defaulting a missing BITRISE_IO_PARALLEL_INDEX to 0 could make every parallel copy run the first row if the env var is not passed through.

Could we require it so fan-out issues fail visibly?

Suggested change

	run_index="${BITRISE_IO_PARALLEL_INDEX:-0}"
	: "${BITRISE_IO_PARALLEL_INDEX:?BITRISE_IO_PARALLEL_INDEX is required for the parallel e2e-execute-browserstack-run workflow.}"
	run_index="$BITRISE_IO_PARALLEL_INDEX"

[kieran-osgood-shopify]

Good call - Found another spot in phase 5 branch that does the same so ill make the same change there too to