906776 - add & enable the treeclosure.py hook to hg.m.o repository projects/fig

Status: RESOLVED FIXED

(Developer Services :: General, task)

Description

[Armen [:armenzg]]

https://tbpl.mozilla.org/?tree=Fig

Comment 1

[Ed Morley [:emorley]]

Needs the tree closure hook adding to it's hgrc, and then someone (eg me) to add it to tree status.

Comment 2

[Justin Wood (:Callek)]

webops, please make this change.

Comment 3

[Ed Morley [:emorley]]

I'm slightly confused...we have a repos & hooks component, but it's not the right place to action getting a hook added?

Comment 4

[Justin Wood (:Callek)]

(In reply to Ed Morley [:edmorley UTC+1] from comment #3)
> I'm slightly confused...we have a repos & hooks component, but it's not the
> right place to action getting a hook added?

Correct, we manage the dev/code of the actual hooks. We also are required (iirc) to ack any production repo changes (like this), but we (releng) do not have direct access to the repo to actually add the hooks.

You are free to file/move into the releng component going forward though, hal and myself at least will watch it pretty rigorously and ack/move as appropriate.

Comment 5

[hwine]

(In reply to Ed Morley [:edmorley UTC+1] from comment #3)
> I'm slightly confused...we have a repos & hooks component, but it's not the
> right place to action getting a hook added?

Yes -- it's absolutely the right places for you to file the bug. Sometimes we can just redirect them, other times we file separate blockers.

Normally, this would be 2 separate bugs, as two steps need to occur:
 - activate the hook (done by IT)
 - add the tree to the status 

In this case, we'll let you handle the 2nd part :)

Comment 6

[Ed Morley [:emorley]]

(In reply to Hal Wine [:hwine] from comment #5)
>  - add the tree to the status 

Done :-)

Comment 7

[Kendall Libby [:fubar] (he/him)]

Treeclosure hook added to fig.