The focus of this week has been finishing off the Q1 goals.
L10N vcs sync
Regarding l10n, I have this now running in staging, and have to clean up the several workarounds I put in place to manage particular problems, such as:
- locales being defined for a branch, but there being no hg repository for it
- not being allowed to update passed-in configs on-the-fly in mozharness, but l10n configs being different to other vcs sync configs
- not completely failing when one repo fails to exist, but others do exist (“do as much as possible but report on failures”)
- cleaning up error handling
gecko-dev and gecko-projects
This piece is done, but I am quite busy setting up full end-to-end staging tests for it. However, the change is enabling features that are enabled for other repos (namely, generation of git notes, and publishing mappings to mapper). Therefore I would propose a simpler and more pragmatic approach, might be to enable these features in production, and if they fail, to disable again. These are just config settings, and no harm should be done if they fail (they do not affect other parts of the vcs sync process, such as altering SHAs or changing urls of repos to pull from / push to.
This piece is the last main one, but I will be doing that when the ones above are ready.
Other things I’ve touched since last review:
Bug 1031378 – Changes to manifests in b2g-manifest that reference repos that are not mirrored to git.mozilla.org should trigger devs/releng/sheriffs
Bug 1027167 – Publish git-hg mappings to mapper by default from new vcs sync (would currently affect gecko-dev and gecko-projects)
Bug 1023843 – Possible bug in end_to_end_reconfig.sh when using -p option?
Bug 1019438 – end_to_end_reconfig.sh should store logs from manage_foopies.py
Bug 1019434 – update_maintenance_wiki.sh is truncating text content
Bug 1018975 – buildfarm/maintenance/manage_foopies.py not executable
Bug 1018248 – End-to-end reconfig should also update tools version on foopies
Bug 1018118 – Growing pending queues for tegras and time between jobs per tegra x3e 6 hours
Bug 1013511 – (byebyebuildduty) [tracking] Eliminate buildduty
Bug 1010173 – test root internal variable on devices (SUTAgentAndroid.sTestRoot) should not be set as an error message
Bug 978928 – Reconfigs should be automatic, and scheduled via a cron job
Bug 976490 – build-tools: Can’t push /opt/vcs2vcs/vcs_sync/build/conversion/build-tools to build-tools-github!
Bug 976106 – tegra/panda health checks (verify.py) should not swallow exceptions
Bug 976100 – Slave Health should link to the watcher log files of the tegras and pandas
Bug 962853 – vcs-sync needs to be able to publish git-hg mappings to mapper
Bug 946019 – cut over gecko.git to the new vcs-sync system
Bug 939817 – more vcs-sync email tweaks
Bug 929336 – permanent location for vcs-sync mapfiles, status json, logs
Bug 904176 – reconfigs as a buildbot/jenkins job
Bug 892691 – Add HD Panda chassis to android production pandas
Bug 876715 – Determine how to update watcher
Bug 875843 – Investigate using distcc for builds (on as many platforms as possible) to reduce build wall clock time
Bug 869051 – Race condition between builders that push updates to in-tree files
Bug 862910 – cache MAR + installer downloads in update verify
Bug 850743 – Clean up / redesign of configuration in buildbot-configs/mozilla
Bug 799845 – For git mirrored repositories, please provide status on what the last successfully sync time was
Bug 770428 – Cleanup org.mozilla.f3nn3c.PasswordsProvider in verify.py
Bug 742479 – Tegra Cleanup should delete some additional files on the sdcard
Bug 686337 – Android nightly builds should download the previous.apk *before* uploading a new gecko-unsigned-unaligned.apk to the same URL