Sheriffing/Backout-setup: Difference between revisions
(Created page with "In order to do backout's and checkins some setup is needed 1.) make sure you have mercurial installed 2.) Clone Repos that we as sheriff maintain like mozilla-central, mozil...") |
(No difference)
|
Latest revision as of 07:12, 6 July 2016
In order to do backout's and checkins some setup is needed
1.) make sure you have mercurial installed 2.) Clone Repos that we as sheriff maintain like mozilla-central, mozilla-inbound, fx-team and autoland 3.) customize your .hg/hgrc of that trees as example my one for mozilla-inbound looks :
[paths] default = http://hg.mozilla.org/integration/mozilla-inbound default-push = ssh://hg.mozilla.org/integration/mozilla-inbound [ui] username = Carsten "Tomcat" Book <cbook@mozilla.com> merge = internal:merge [extensions] qbackout = /sheriffs/trees/version-control-tools/hgext/qbackout histedit = progress = rebase = mq = qimportbz = /sheriffs/trees/version-control-tools/hgext/qimportbz transplant = [alias] rbimport = !hg transplant -e -s https://reviewboard-hg.mozilla.org/gecko -b $1
The whole backout is simple:
As example a developer asks you to backout changeset ab1234 so the command for the backout would be
hg qbackout -r ab1234 && hg qrefresh -e
The hg qbackout -r <revision> should contain the revision you will backout. The hg qrefresh -e command allows you to edit the commit message for the backout, like why you backout something (example for bustage).
Backout multiple changsets ?
As example you need to backout a push that had multiple changesets/parts, the command would be
hg qbackout -r firstcset -r 2ndcset && hg qrefresh -e