| Summary: | Add git hook to update bug status | ||
|---|---|---|---|
| Product: | [Infrastructure] Bugzilla | Reporter: | Michael Wood <michael.g.wood> |
| Component: | bugzilla | Assignee: | Ross Burton <ross.burton> |
| Status: | NEW --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium | CC: | alex.kanavin, bluelightning, infras.bug.watcher, Infras.watcher, mhalstead, randy.macleod, richard.purdie, ross.burton |
| Version: | unspecified | ||
| Target Milestone: | Future | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| See Also: | https://bugzilla.yoctoproject.org/show_bug.cgi?id=9817 | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Michael Wood
2015-02-16 17:38:23 UTC
The consensus is that we wouldn't want to mark bugs resolved automatically, however we should be at the very least adding a comment to the bug with a link to the commit. Richard raised another concern that this should not impose additional time on his process of pushing changes, so it would have to be either completely independent of the pushing client, or a process that simply gets triggered at the end of pushing and asynchronously does the bugzilla updates on a server somewhere. We may do this from patchwork rather than from a separate script, since that's already triggered when commits are pushed to the git repository. I was reminded about this by looking at a bug in glibc, which does comment in bugs when a commit references the bug. As we agreed it doesn't do anything apart from leave a comment: https://sourceware.org/bugzilla/show_bug.cgi?id=20019#c14 Gitzilla (https://github.com/gera/gitzilla) appears to make this fairly simple, and the reminder that a patch has landed will be very useful to ensure bugs are closed and alert users that their bugs are resolved. Is there any chance we can get this done sooner rather than later? Would you expect the bugzilla entry to be similar to the sourceware comment you linked to? Yes, similar, the commit log and patch summary would be good to help identify what landed. *** Bug 9817 has been marked as a duplicate of this bug. *** A script rather than a git hook is what people prefer. Ross claims to have a starting point. So some time ago I wrote a little script that looks through the git history (up to a certain point), looking for mentioned bugs that are still open: https://github.com/rossburton/ross-tools/blob/master/git-find-bugs No idea if it still works... |