Closed Bug 464974 Opened 13 years ago Closed 13 years ago

Add "closed tree" hook to mozilla-central

Categories

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

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: johnath, Assigned: aravind)

References

Details

Now that we have landed the treeclosure.py hook in bug 458172, the next step is to wire it up to mozilla-central.

It's a pretxnchangegroup, so this should just mean adding:

pretxnchangegroup = python:mozhghooks.treeclosure.hook

to the [hooks] section.  But you knew that.

Gonna write a dev.planning note about this too, in case anyone thinks of a reason it shouldn't be done - but it's pretty easy to flip on and off, so I don't really think we should block this bug on that discussion...
Depends on: 458172
There seems to be broad agreement on the dev.planning thread so far.  Let's do it.
how is it enabled?  I am guessing it needs IT intervention everytime this needs to be activated?  Also, does it turn on automatically once I add it to the hooks section?
Assignee: server-ops → aravind
(In reply to comment #2)
> how is it enabled?  I am guessing it needs IT intervention everytime this needs
> to be activated?  Also, does it turn on automatically once I add it to the
> hooks section?

No IT intervention needed - it scrapes the tinderbox page (which sheriffs already update to signal a closed tree) and in every case except where it finds "CLOSED" in the span tag it is looking at, it lets the checkin through.

It's live as soon as you add it to the hgrc.
Done.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Blocks: 465566
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.