Modify ↓
Opened 18 years ago
Last modified 9 years ago
#4746 new enhancement
intertrac links support in trac-post-commit hook
Reported by: | philn | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | unscheduled |
Component: | version control | Version: | |
Severity: | normal | Keywords: | post-commit hook intertrac |
Cc: | jeffhung@…, Ryan J Ollos | Branch: | |
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
Hello,
It would be very nice to support intertrac links within the trac-post-commit hook. If the XMLRPC plugin is installed in the remote trac, tickets should be remotely updateable.
Attachments (1)
Change History (7)
comment:1 by , 18 years ago
Component: | ticket system → version control |
---|---|
Keywords: | post-commit hook intertrac added |
Milestone: | 0.10.4 → 1.0 |
Owner: | changed from | to
comment:2 by , 17 years ago
Cc: | added |
---|
by , 13 years ago
Attachment: | patch-tracopt__ticket__commit_updater.py added |
---|
Adds support for intertrac links to allow updating a specific trac instance. It is using the project_name as it's own intertrac prefix.
comment:4 by , 13 years ago
Cc: | added |
---|
comment:6 by , 10 years ago
Cc: | added; removed |
---|
comment:7 by , 9 years ago
Owner: | removed |
---|
Note:
See TracTickets
for help on using tickets.
Hm, I see one scenario where this could make sense: it would be for a Subversion repository which is actually shared between multiple projects/Trac instances…
In that scenario, it's true that when you want to close a ticket by the way of the trac-post-commit-hook, you need a way to specify which project you're actually targeting, and this could be done using InterTrac prefixes, yes.
However, I see this more related to the multiple repository support (#2086) and the multiple project support (#130), as doing this with XML-RPC for targeting remote Tracs is I think quite outside the scope of Trac core (not to mention the latency issues you'd get when trying to commit, if such a hook was ever used…).