Releases/Firefox 34.0/BuildNotes: Difference between revisions

→‎Running tests: more details
(→‎Fennec 34.0 build1: repack green, wonky emal)
(→‎Running tests: more details)
Line 42: Line 42:


==== Running tests ====
==== Running tests ====
We may be able to commit the config patch to tools, then force the beta update verify jobs using the revision that landed ?
Rather than grabbing 3 slaves and running these manually, we may be able to twist the automation's arm:
* wait until we get the 'updates available on betatest' email
* commit the config patch to tools (no fallout from this on next release)
* force the beta update verify jobs (eg release-mozilla-beta-linux_update_verify_1/6). We'd need to set the '''script_repo_revision''' property to the revision when that landed


= Fennec 34.0 build1 =
= Fennec 34.0 build1 =
Confirmed users
4,293

edits