Account confirmers, Anti-spam team, Confirmed users, Bureaucrats and Sysops emeriti
1,529
edits
ReleaseEngineering/TryServer: Difference between revisions
ReleaseEngineering/TryServer (view source)
Revision as of 17:53, 7 September 2016
, 7 September 2016l10n jobs
m (The bug preventing us from scheduling pushes beyond a week has landed) |
(l10n jobs) |
||
| Line 109: | Line 109: | ||
The resulting builds are uploaded to the same sub-directory as en-US builds, eg try-linux/ for 32bit linux. | The resulting builds are uploaded to the same sub-directory as en-US builds, eg try-linux/ for 32bit linux. | ||
== Desktop l10n jobs (on Taskcluster) == | |||
To get Desktop l10n jobs on taskcluster on try, simply pass `-p linux64-l10n,linux-l10n` with your try push. You'll also get these jobs automatically with `-p linux64,linux` if you are touching one of the files known to be heavily involved in l10n jobs. (Taskcluster support for other platforms is not yet available) | |||
You can also use the steps in [[ReleaseEngineering/TryServer#Scheduling jobs with Treeherder|Scheduling jobs with Treeherder]] to add localized desktop builds to your try push, regardless of whether you used try syntax at first. Filtering with 'l10n' helps to find the jobs amongst the many possibilities. | |||
The jobs can be customized by modifying files prior to pushing: | |||
* reducing the number of locales by limiting <tt>browser/locales/all-locales</tt> (eg top-locales like de fr ja ja-JP-mac ru zh-TW). | |||
* use a different en-US build by modifying [https://dxr.mozilla.org/mozilla-central/source/testing/mozharness/configs/single_locale/try.py#4 en_us_binary_url], but note that the building en-US and then l10n in one push is not a tested scenario | |||
* use the Aurora l10n repos by modifying [https://dxr.mozilla.org/mozilla-central/source/testing/mozharness/configs/single_locale/try.py#10 hg_l10n_base] | |||
The resulting builds are uploaded as a task artifact, and are not yet signed. | |||
== Android Single-Locale l10n jobs (on Taskcluster) == | |||
(NOTE: Only supported on Gecko 51a1 and above) | |||
To get Android l10n jobs on taskcluster on try, simply pass `-p android-api-15-l10n` with your try push. You'll also get these jobs automatically with `-p android-api-15` if you are touching one of the files known to be heavily involved in l10n jobs. | |||
You can also use the steps in [[ReleaseEngineering/TryServer#Scheduling jobs with Treeherder|Scheduling jobs with Treeherder]] to add localized desktop builds to your try push, regardless of whether you used try syntax at first. Filtering with 'l10n' helps to find the jobs amongst the many possibilities. | |||
The jobs can be customized by modifying files prior to pushing: | |||
* reducing the number of locales by limiting <tt>mobile/android/locales/all-locales</tt> (eg top-locales like de fr ru zh-TW). | |||
* use a different en-US build by modifying [https://dxr.mozilla.org/mozilla-central/source/testing/mozharness/configs/single_locale/try_android-api-15.py#3 en_us_binary_url], but note that the building en-US and then l10n in one push is not a tested scenario | |||
* use the Aurora l10n repos by modifying [https://dxr.mozilla.org/mozilla-central/source/testing/mozharness/configs/single_locale/try_android-api-15.py#42 hg_l10n_base] | |||
The resulting builds are uploaded as a task artifact, and are not yet signed. | |||
== Server Status == | == Server Status == | ||