Bug 1351306 - Move the UTC starttime of nightlies earlier. r=rail
This is needed because we want to keep the nightly start times aligned with Buildbot starts, in order to keep the possibility of drastically different code going out for one platform in a day and not another (e.g. a merge). The reason the change is needed specifically is because UTC of course doesn't follow Daylight Time shifts, and Pacific time just went through one (+1 hour) which brings it closer to UTC by one hour, so in order to keep UTC matching what buildbot uses we subtract 1 hour from the UTC time.
MozReview-Commit-ID: J07lZYJxlOd
--- a/.cron.yml
+++ b/.cron.yml
@@ -11,37 +11,37 @@ jobs:
target-tasks-method: nightly_linux
run-on-projects:
- mozilla-central
- mozilla-aurora
- date
when:
by-project:
# Match buildbot starts for now
- date: [{hour: 16, minute: 0}]
- mozilla-central: [{hour: 11, minute: 0}]
- mozilla-aurora: [{hour: 8, minute: 45}] # Buildbot uses minute 40
+ date: [{hour: 15, minute: 0}]
+ mozilla-central: [{hour: 10, minute: 0}]
+ mozilla-aurora: [{hour: 7, minute: 45}] # Buildbot uses minute 40
# No default
- name: nightly-android
job:
type: decision-task
treeherder-symbol: Na
triggered-by: nightly
target-tasks-method: nightly_fennec
run-on-projects:
- mozilla-central
- mozilla-aurora
- date
when:
by-project:
# Match buildbot starts for now
- date: [{hour: 16, minute: 0}]
- mozilla-central: [{hour: 11, minute: 0}]
- mozilla-aurora: [{hour: 8, minute: 45}] # Buildbot uses minute 40
+ date: [{hour: 15, minute: 0}]
+ mozilla-central: [{hour: 10, minute: 0}]
+ mozilla-aurora: [{hour: 7, minute: 45}] # Buildbot uses minute 40
# No default
- name: nightly-mochitest-valgrind
job:
type: decision-task
treeherder-symbol: Vg
target-tasks-method: mochitest_valgrind
run-on-projects: