Opened 17 years ago
Last modified 8 years ago
#6135 new enhancement
Enhancement for trac-post-commit-hook.py for Enterprise Workflow
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | unscheduled |
Component: | general | Version: | |
Severity: | normal | Keywords: | enterprise workflow, postcommit hook, CommitTicketUpdater |
Cc: | shansen@… | Branch: | |
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
Enhancement for trac-post-commit-hook.py for Trac Enterprice Workflow.
Attachments (2)
Change History (17)
by , 17 years ago
Attachment: | trac-post-commit-hook_for-enterprice-workflow.py added |
---|
comment:1 by , 17 years ago
Priority: | normal → high |
---|---|
Summary: | Enhancement for trac-post-commit-hook.py for Enterprice Workflow → Enhancement for trac-post-commit-hook.py for Enterprise Workflow |
comment:2 by , 17 years ago
It would be useful (and greatly increase your chances of this getting merged) if this was presented as a diff file so we can see the code changes, and also if you can explain what the changes are and how they are helpful.
comment:4 by , 17 years ago
I wonder at the utility of this change, as I re-convert back to the trac world and blink in surprise at the old script I threw together seems to have been maintained all this time. That rocks, lol. :)
Anyways: as I fiddle and configure up our "enterprise workflow", what leaps out at me is that the change to the hook provided here makes two assumptions that seem dramatically wrong for me… and I wonder if they're wrong for others.
In my "Enterprise" setup, developers never close tickets. The most a developer does is claim to have fixed it, and send it to the QA bucket where it is then verified by someone else who has the right to close the ticket.
Secondly, the QA department never commits to the repository.
I'm thinking of working up a configurable hook that can suit either the OP's need or my own, whereby a commit message that claims to 'fix' a ticket actually just transfers it to QA. Must dig further into the internals first. :)
comment:5 by , 17 years ago
Cc: | added |
---|
by , 17 years ago
Attachment: | workflow-post-commit-hook.patch added |
---|
workflow-aware version of trac-post-commit-hook
comment:6 by , 17 years ago
Since the workflow-enabling was easier then I thought, I attached a patch for a suggested alternate implementation then the one originally suggested in the ticket. Should be tweakable to be compatible to my original hook, and configurable to do what the original poster wanted (a 'test' / 'verify' command), in addition to my own needs. I think! Works for me at least :)
comment:8 by , 16 years ago
I had to add self.args = {
} to DummyRequest
's __init__
method in order for all actions to work properly.
comment:10 by , 16 years ago
Milestone: | 0.11-retriage → 0.12 |
---|
The post-commit-hook will have to be redesigned anyway on top of the IChangesetListener interface brought by #7723.
comment:11 by , 15 years ago
Keywords: | enterprise workflow postcommit added; Enterprice Workflow post commit removed |
---|---|
Milestone: | 0.12 → 0.13 |
This will have to updated w.r.t. the new CommitTicketUpdatePlugin (see r8094).
comment:13 by , 14 years ago
Milestone: | next-major-0.1X → unscheduled |
---|---|
Priority: | high → normal |
comment:14 by , 9 years ago
Owner: | removed |
---|
comment:15 by , 8 years ago
Keywords: | CommitTicketUpdater added; CommitTicketUpdate removed |
---|
Enhancement for Enterprise Workflow