Skip to content

Commit 82820b0

Browse files
devversionbenlesh
authored andcommitted
ci: run saucelabs legacy tests every hour (angular#28903)
Initially when we introduced the cronjob for Saucelabs, we specified that the tests should run every 4h. Since the caretaker needs more recent results when merging PRs or before creating a release, we should run the saucelabs tests every hour. This still ensures that PRs are not affected by Saucelabs flakiness or incidents, and the caretaker can also react better to real browser failures (and isn't blocked on a 4h time frame) PR Close angular#28903
1 parent 1778bd3 commit 82820b0

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

.circleci/config.yml

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -615,8 +615,12 @@ workflows:
615615
- legacy-unit-tests-saucelabs
616616
triggers:
617617
- schedule:
618-
# Runs the Saucelabs legacy tests every four hours.
619-
cron: "0 0,4,8,12,16,20 * * *"
618+
# Runs the Saucelabs legacy tests every hour. We still want to run Saucelabs
619+
# frequently as the caretaker needs up-to-date results when merging PRs or creating
620+
# a new release. Also we primarily moved the Saucelabs job into a cronjob that doesn't
621+
# run for PRs, in order to ensure that PRs are not affected by Saucelabs flakiness or
622+
# incidents. This is still guaranteed (even if we run the job every hour).
623+
cron: "0 * * * *"
620624
filters: *publish_branches_filter
621625

622626
aio_monitoring:

0 commit comments

Comments
 (0)