Closed Bug 560920 Opened 16 years ago Closed 16 years ago

Remove no-multiple-heads hg hook from build/buildbot-configs, build/buildbotcustom

Categories

(mozilla.org Graveyard :: Server Operations, task)

All
Other
task
Not set
major

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: catlee, Assigned: aravind)

Details

Please remove the hg hook that prevents multiple heads from landing on our build/buildbot-configs and build/buildbotcustom repositories. Is there a hook that enforces a single head per named branch? If so, we'd like that!
We can't land anything on default currently because of this. If this is blocked on something, I can back out catlee's branch, but I'm hoping this is quick?
Severity: minor → major
Assignee: server-ops → aravind
You currently have this hook for that repo. [hooks] pretxnchangegroup.a_singlehead = /repo/hg/scripts/hg_require_single_head I changed it to this. [hooks] pretxnchangegroup.a_singlehead = python:mozhghooks.single_head_per_branch.hook
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
When does this take effect? akira-sasakis-macbook:buildbot-configs asasaki$ hg branches default 2328:b36250b7d4c8 buildbot-0.8.0 2327:77d10fffd0ae akira-sasakis-macbook:buildbot-configs asasaki$ hg ident b36250b7d4c8 tip akira-sasakis-macbook:buildbot-configs asasaki$ hg pull pulling from http://hg.mozilla.org/build/buildbot-configs searching for changes no changes found akira-sasakis-macbook:buildbot-configs asasaki$ hg up -r default 0 files updated, 0 files merged, 0 files removed, 0 files unresolved akira-sasakis-macbook:buildbot-configs asasaki$ hg push -f pushing to ssh://hg.mozilla.org/build/buildbot-configs searching for changes remote: adding changesets remote: adding manifests remote: adding file changes remote: added 1 changesets with 1 changes to 1 files (+1 heads) remote: You may not push multiple heads to this repository. remote: transaction abort! remote: rollback completed remote: abort: pretxnchangegroup.a_singlehead hook exited with status 1 abort: unexpected response: empty string
Oh sorry, I had only enabled it for buildbotcustom, I have now enabled it for buildbot-configs as well.
Yay! Was able to push to buildbot-configs with push -f. Thanks Aravind!
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.