Граф коммитов

9 Коммитов

Автор SHA1 Сообщение Дата
Gregory Szorc 802fda3e66 Bug 1270317 - Use robustcheckout extension for checking out Mercurial repos; r=jlund
Functionality for doing an optimal clone/pull+share+purge+update is now
implemented in the robustcheckout extension so it can be implemented in one
place and used by all the various tools needing to perform a "robust"
checkout using optimal practices.

This commit switches the MercurialVCS to use it.

Functionality for interfacing with shared repos and associated tests have
been removed because this is all implemented and tested in robustcheckout.

Various other tests have also been removed because they are redundant with
tests in the robustcheckout extension.

MozReview-Commit-ID: FGvmSHKM5e0

--HG--
extra : rebase_source : 8f31a1e79d448478fa63b17582313409ac06fe69
extra : histedit_source : 3031dd8f83b0c64abc110252fd270f1917168663
2016-05-16 16:56:14 -07:00
Carsten "Tomcat" Book 5257224b2f Backed out changeset 86fccb7da8ac (bug 1270317) 2016-05-09 12:34:04 +02:00
Gregory Szorc 9bda169114 Bug 1270317 - Use modern, optimal cloning in MercurialVCS.ensure_repo_and_revision(); r=jlund
The code for ensure_repo_and_revision() has been completely overhauled.

We now require shared repos using auto pooled storage via the share
extension. This ensures that only a single copy of a logical
repository's history is stored on disk. e.g. if you clone
mozilla-central, inbound, and try, they'll all automatically share the
same storage.

The new code ensures the destination repo is using modern conventions
and will delete the destination repo if it isn't. So once this gets
deployed to production, machines will slowly start using optimal
storage. This should make VCS operations significantly faster.

Another optimization that is now in here is we check for presence of the
wanted revision before doing `hg pull`. This saves some communication
with the server if the revision is already present locally.

This change effectively requires a modern version of Mercurial to be
installed to run ensure_repo_and_revision(). Since Mercurial <3.7.3 has
security vulnerabilities, we shouldn't be running <3.7.3 in automation.
So I think this will be OK. If not, it will certainly be easy to
identify which machines aren't updated!

MozReview-Commit-ID: 62jtAsDj7rU

--HG--
extra : rebase_source : a43d7f54b16e71940e45ddf05402449575fccfee
2016-05-06 10:57:28 -07:00
Rail Aliiev 942056deee Bug 1210539 - Add "updates" builder to release promotion task r=jlund DONTBUILD a=release
--HG--
rename : testing/mozharness/mozharness/mozilla/merge.py => testing/mozharness/mozharness/mozilla/repo_manupulation.py
extra : rebase_source : c8a8a2891fcdc50111e497acd33262c295da1ba2
2016-02-19 12:53:03 -08:00
Carsten "Tomcat" Book 6244cfb10e Backed out changeset 200da85932e9 (bug 1230862) for valgrind perma failures 2016-02-10 11:04:50 +01:00
Julien Pagès cb348f4346 Bug 1230862 - Remove mozhttpd. r=wlach
--HG--
extra : commitid : HRDp24nhYo8
extra : rebase_source : 76443fa9938e488fcd06af7ba0676d491c9da36e
2016-02-09 03:26:43 +01:00
Aki Sasaki 081f08c2ae bug 1244781 - mozharness has 3 post_run listeners now. r=jlund
--HG--
extra : histedit_source : ce94bf5ad5e3abe96ec3c75839ed581af134a487
2016-02-02 14:11:05 -05:00
Mike Shal 115ca1ae64 Bug 1192068 - Use long hg revision for sourcestamp in mozharness; r=gps,jlund 2015-08-06 15:39:38 -04:00
Jordan Lund 8405b45930 Bug 1154796 - make a copy of mozharness and put it in gecko tree, based on 4d855a6835ed, r=mshal 2015-07-03 09:04:58 -07:00