Changes between Version 2 and Version 3 of OneRepoManyTracSitesPatch
- Timestamp:
- Aug 6, 2016, 10:22:29 PM (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
OneRepoManyTracSitesPatch
v2 v3 5 5 == Description 6 6 7 We have multiple repositories and multiple Trac sites. Our users expressed a need to be ableto update tickets on multiple Trac sites from a single commit comment in a repository.7 This plugin allows you to update tickets on multiple Trac sites from a single commit comment in a repository. 8 8 9 For example, consider the commit:9 We have multiple repositories and multiple Trac sites. For example, consider the commit: 10 10 {{{ 11 11 Updated the foo to fix the bar. … … 15 15 }}} 16 16 17 Our problem was that ticket 71 existed in TracSiteA, and ticket 42 existed in TracSiteB. On TracSiteA, the comment would be added to ticket 71 and 42, but ticket 42 on TracSiteA had nothing to do with the issue.Similarly on TracSiteB, the comment would be added to ticket 42, with an unknown link to the non-existent ticket 71 on that site.17 Our problem was that ticket 71 existed in TracSiteA, and ticket 42 existed in TracSiteB. On TracSiteA, the comment would be added to ticket 71 and 42, but ticket 42 on TracSiteA had nothing to do with the issue. Similarly on TracSiteB, the comment would be added to ticket 42, with an unknown link to the non-existent ticket 71 on that site. 18 18 19 This patch enables our users to commit thusly:19 This patch enables our users to commit as follows: 20 20 {{{ 21 21 Updated the foo to fix the bar. … … 25 25 }}} 26 26 27 The comments only get added to TracSiteA ticket 71 and TracSiteB ticket 42. As some added gravy this patch also converts the comments so that the links take the user to the correct place.27 The comments only get added to TracSiteA ticket 71 and TracSiteB ticket 42. 28 28 29 For example, the source of the comment on ticket 71 of TracSiteA would appear as... 29 This patch also converts the comments so that the links take the user to the correct place. For example, the source of the comment on ticket 71 of TracSiteA would appear as follows: 30 30 {{{ 31 31 Updated the foo to fix the bar. … … 34 34 See [[http://mytracsite.com/TracSiteB/ticket/42|#42@TracSiteB]] as well 35 35 }}} 36 ...and the source of the comment on ticket 42 of TracSiteB would appear as... 36 37 ...and the source of the comment on ticket 42 of TracSiteB would appear as follows: 37 38 {{{ 38 39 Updated the foo to fix the bar. … … 41 42 See #42@TracSiteB as well 42 43 }}} 43 ... this way links created in the comment don't take our users to confusing places. 44 45 This way links created in the comment don't take our users to confusing places. 44 46 45 47 == !Bugs/Feature Requests … … 65 67 Apply the patch to tracopt/ticket/commit_updater.py. 66 68 67 Update your trac.ini file.Following the scenario in the description:69 Update your `trac.ini` file. Following the scenario in the description: 68 70 69 TracSiteA's ini has ...70 {{{ 71 TracSiteA's ini has the following: 72 {{{#!ini 71 73 [ticket] 72 74 commit_ticket_update_name_is_required = true … … 75 77 TracSiteB = http://mytracsite.com/TracSiteB/ticket/ 76 78 }}} 77 ...and TracSiteB's ini has... 78 {{{ 79 80 And TracSiteB's ini has the following: 81 {{{#!ini 79 82 [ticket] 80 83 commit_ticket_update_name_is_required = true … … 83 86 TracSiteA = http://mytracsite.com/TracSiteA/ticket/ 84 87 }}} 85 86 88 87 89 == Recent Changes
