Edgewall Software

Ticket #6135 (new enhancement)

Opened 12 months ago

Last modified 5 months ago

Enhancement for trac-post-commit-hook.py for Enterprise Workflow

Reported by: vinogradniy@… Owned by: jonas
Priority: high Milestone: 0.11.3
Component: general Version:
Severity: normal Keywords: Enterprice Workflow, post commit hook
Cc: shansen@…

Description

Enhancement for trac-post-commit-hook.py for Trac Enterprice Workflow.

Attachments

trac-post-commit-hook_for-enterprice-workflow.py (8.6 kB) - added by vinogradniy@… 12 months ago.
Enhancement for Enterprise Workflow
workflow-post-commit-hook.patch (11.2 kB) - added by shansen@… 9 months ago.
workflow-aware version of trac-post-commit-hook

Change History

Changed 12 months ago by vinogradniy@…

Enhancement for Enterprise Workflow

Changed 12 months ago by anonymous

  • priority changed from normal to high
  • summary changed from Enhancement for trac-post-commit-hook.py for Enterprice Workflow to Enhancement for trac-post-commit-hook.py for Enterprise Workflow

Changed 12 months ago by sid

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.

Changed 11 months ago by cboos

  • milestone changed from 0.11 to 0.11.1

Maybe for 0.11.1.

Changed 9 months ago by shansen@…

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. :)

Changed 9 months ago by anonymous

  • cc shansen@… added

Changed 9 months ago by shansen@…

workflow-aware version of trac-post-commit-hook

Changed 9 months ago by shansen@…

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 :)

Changed 5 months ago by matt@…

How would I implement this into my trac install?

Changed 5 months ago by rock@…

I had to add self.args = {} to DummyRequest's __init__ method in order for all actions to work properly.

Add/Change #6135 (Enhancement for trac-post-commit-hook.py for Enterprise Workflow)

Author



Change Properties
<Author field>
Action
as new
as The resolution will be set. Next status will be 'closed'
to The owner will change from jonas. Next status will be 'new'
The owner will change from jonas to anonymous. Next status will be 'assigned'
 
Note: See TracTickets for help on using tickets.