ci: run saucelabs legacy tests every hour (#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 #28903
This commit is contained in:
Paul Gschwendtner 2019-02-21 22:28:17 +01:00 committed by Ben Lesh
parent 1778bd3470
commit 82820b0b2c
1 changed files with 6 additions and 2 deletions

View File

@ -615,8 +615,12 @@ workflows:
- legacy-unit-tests-saucelabs - legacy-unit-tests-saucelabs
triggers: triggers:
- schedule: - schedule:
# Runs the Saucelabs legacy tests every four hours. # Runs the Saucelabs legacy tests every hour. We still want to run Saucelabs
cron: "0 0,4,8,12,16,20 * * *" # frequently as the caretaker needs up-to-date results when merging PRs or creating
# a new release. Also we primarily moved the Saucelabs job into a cronjob that doesn't
# run for PRs, in order to ensure that PRs are not affected by Saucelabs flakiness or
# incidents. This is still guaranteed (even if we run the job every hour).
cron: "0 * * * *"
filters: *publish_branches_filter filters: *publish_branches_filter
aio_monitoring: aio_monitoring: