Closed Bug 1557070 Opened 5 years ago Closed 5 years ago

Upgrade hg.mozilla.org to Mercurial 5.0.1

Categories

(Developer Services :: Mercurial: hg.mozilla.org, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: sheehan, Assigned: sheehan)

References

Details

(Keywords: leave-open)

Attachments

(9 files)

47 bytes, text/x-phabricator-request
Details | Review
47 bytes, text/x-phabricator-request
Details | Review
47 bytes, text/x-phabricator-request
Details | Review
47 bytes, text/x-phabricator-request
Details | Review
47 bytes, text/x-phabricator-request
Details | Review
47 bytes, text/x-phabricator-request
Details | Review
47 bytes, text/x-phabricator-request
Details | Review
47 bytes, text/x-phabricator-request
Details | Review
47 bytes, text/x-phabricator-request
Details | Review

A new point-release has been cut, we should upgrade the server to this version.

This is also a Py3 beta release, so we can start experimenting with using Py3 in our virtualenvs once we have completed this upgrade.

Keywords: leave-open
Pushed by cosheehan@mozilla.com:
https://hg.mozilla.org/hgcustom/version-control-tools/rev/66ab2b86fdc2
testing: upgrade to Mercurial 5.0.1 in testing

Also mark as compatible with Mercurial 5.0

Also mark as compatible with Mercurial 5.0.

Depends on D33846

Only a minor test change needed for passing tests. The test
in question is related to wire protocol version two, which
can arguably be removed anyways.

Depends on D33847

Tests are passing without any changes, with the exception of
a single test which fails due to a changed API used by a helper
script. This commit updates the helper script to use the new
APIs and marks the hghooks extension as compatible with
5.0.

Depends on D33848

This version should always match the version running on hg.mo,
which means it needs to be bumped during the upgrade. Running
this test should tell us if we have any outstanding template
upgrades to perform, and since it passes without issue, we
don't need to make any template changes.

Depends on D33849

No changes needed to get these extensions passing under 5.0.

Depends on D33850

This commit upgrades to Mercurial 5.0 in all locations that do not
run on hg.mozilla.org (testing, docs and deploy environments).

Depends on D33851

This commit upgrades Mercurial to 5.0.1 on hgssh in all
virtual environments. This commit should be deployed first
in the upgrade process.

Depends on D33852

This commit upgrades Mercurial to 5.0.1 in all virtual environments
on hgweb.

Depends on D33853

Pushed by cosheehan@mozilla.com:
https://hg.mozilla.org/hgcustom/version-control-tools/rev/0461ff7338e8
pushlog: add new output to `test-pull-obsolete.t` r=glob
https://hg.mozilla.org/hgcustom/version-control-tools/rev/465163f8a58a
overlay: rename `copied` keyword argument to `copysource` under 5.0+ r=glob
https://hg.mozilla.org/hgcustom/version-control-tools/rev/cca19bee710d
hgmo: mark as compatible with Mercurial 5.0 r=glob
https://hg.mozilla.org/hgcustom/version-control-tools/rev/df232910b213
hghooks: enable test compatibility under Mercurial 5.0 r=glob
https://hg.mozilla.org/hgcustom/version-control-tools/rev/4b32cf190f59
hgtemplates: run `test-template-sync.t` against Mercurial 5.0.1 r=glob
https://hg.mozilla.org/hgcustom/version-control-tools/rev/25a0f6ca4c3b
hg50: mark many extensions as compatible with Mercurial 5.0 r=glob
https://hg.mozilla.org/hgcustom/version-control-tools/rev/541dd5aba62d
testing: upgrade to Mercurial 5.0 in testing and miscellaneous locations r=glob
https://hg.mozilla.org/hgcustom/version-control-tools/rev/55f71016659c
ansible/hg-ssh: upgrade to Mercurial 5.0.1 r=glob
https://hg.mozilla.org/hgcustom/version-control-tools/rev/cd14589c8543
ansible/hg-web: upgrade to Mercurial 5.0.1 r=glob

hg.mozilla.org is now running 5.0.1 on all servers (hgssh, public hg and mirrors).

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: