Version Control in CI¶
Upgrading Mercurial in CI requires touching a handful of different components.
robustcheckout Mercurial extension is used throughout CI to
perform clones and working directory updates. The canonical home of
the extension is in the
at the path
When upgrading Mercurial, the
robustcheckout extension should also
be updated to ensure it is compatible with the version of Mercurial
being upgraded to. Typically, one simply copies the latest version
version-control-tools into the vendored locations.
The locations are as follows:
Debian Packages for Debian and Ubuntu Based Docker Images¶
define custom Debian packages for Mercurial. These are installed in various
To upgrade Mercurial, typically you just need to update the source URL and its hash in this file.
https://github.com/mozilla-releng/OpenCloudConfig defines the Windows
environment for various Windows AMIs used by Taskcluster. Several of
the files reference a
mercurial-x.y.z-*.msi installer. These references
will need to be updated to the Mercurial version being upgraded to.
robustcheckout extension is also vendored into this repository
should also be updated if needed.
Puppet Maintained Hosts¶
Some hosts (namely macOS machines) are managed by Puppet and Puppet is used to install Mercurial.
Puppet code lives in the https://github.com/mozilla-releng/build-puppet repository.
Relevant files are in
modules/packages/manifests/mozilla/py27_mercurial*. A copy of
robustcheckout is also vendored at
The steps to upgrade Mercurial in Puppet aren’t currently captured here. Someone should capture those…