Closed Bug 887184 Opened 11 years ago Closed 11 years ago

Commit message hook should exempt gaia.json auto-commits

Categories

(Developer Services :: Mercurial: hg.mozilla.org, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: emorley, Assigned: emorley)

References

Details

Attachments

(1 file, 1 obsolete file)

I've just hit the commit message hook trying to merge birch to mozilla-central, due to gaia.json auto commits that do not contain a bug number.

We should:
1) Make the commit message hook exempt "Bumping gaia.json".
2) Switch on the commit message hook for birch, so we catch things before merging to m-c.

This bug covers #1.
Filed bug 887193 for #2.
Attached patch Patch v1 (obsolete) — Splinter Review
Exempts gaia.json auto commits [1] & removes the now redundant nanojit-import exemption (nanojit is no longer in the tree as of bug 698201).


[1] Example: https://hg.mozilla.org/mozilla-central/rev/b77e4465858c
Attachment #767683 - Flags: review?(evilpies)
Comment on attachment 767683 [details] [diff] [review]
Patch v1

Review of attachment 767683 [details] [diff] [review]:
-----------------------------------------------------------------

Have you considered checking the user instead of the commit message? We already check for some users, but I am not even sure what they all are.
Attachment #767683 - Flags: review?(evilpies) → review+
Attached patch Patch v2Splinter Review
Yeah let's do that instead. Also removes two unnecessary imports that pyflakes was complaining about.
Attachment #767745 - Flags: review?(evilpies)
Attachment #767683 - Attachment is obsolete: true
Comment on attachment 767745 [details] [diff] [review]
Patch v2

Review of attachment 767745 [details] [diff] [review]:
-----------------------------------------------------------------

I would feel better if this had a test, but Ed told me that the don't even run for him. :(
Attachment #767745 - Flags: review?(evilpies) → review+
Wouldn't it be simpler to change the gaia.json-bumping script to include "no bug" in the commit message, rather than adding another special case to the hook?
That is more of hack and not the intended purpose of "no bug".
What is "no bug" for, if not for changes which aren't tracked by bugs? I'm not sure the semantic distinction you're making is useful :)
Blocks: 887847
I'm just going to go with the approach in the attached patch:
https://hg.mozilla.org/hgcustom/hghooks/rev/0c5570033c6b
Looks good.
Depends on: 891913
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Product: Release Engineering → Developer Services
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: