You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Bitrise E2E pipeline starts in soft-fail mode:
6
+
7
+
```bash
8
+
E2E_STRICT=false
9
+
```
10
+
11
+
In soft-fail mode, BrowserStack Maestro assertion failures are reported through GitHub commit statuses, Check Runs, and the sticky PR failure comment, but the BrowserStack workflow exits successfully so the initial rollout does not block PR progress.
12
+
13
+
Set `E2E_STRICT=true` only after the suite has stabilized and the corresponding GitHub contexts are ready to become required checks.
14
+
15
+
## Retry behavior
16
+
17
+
BrowserStack API calls retry transient infrastructure responses once by default:
18
+
19
+
```bash
20
+
E2E_BROWSERSTACK_API_RETRIES=1
21
+
```
22
+
23
+
Retry applies to HTTP 429 and 5xx responses. Maestro assertion failures are not auto-retried by default so first-failure evidence is preserved.
24
+
25
+
## Timeouts
26
+
27
+
BrowserStack polling uses these defaults:
28
+
29
+
```bash
30
+
E2E_BROWSERSTACK_TIMEOUT_SECONDS=1800
31
+
E2E_BROWSERSTACK_POLL_SECONDS=30
32
+
```
33
+
34
+
If polling times out, the runner attempts to stop the BrowserStack build before failing or soft-failing according to `E2E_STRICT`.
35
+
36
+
## Local rerun notes
37
+
38
+
Use the matrix row from a failure report to identify the app target, platform, OS track, and suite:
0 commit comments