Changes between Version 19 and Version 20 of TracTicketChangelogPlugin
- Timestamp:
- Mar 13, 2015, 12:20:01 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracTicketChangelogPlugin
v19 v20 19 19 20 20 === Mercurial 21 For mercurial backend, since [http://trac.edgewall.org/ticket/8417 TracMecurial did not support repository cache] yet, you should install [http://github.com/maraujop/TracMercurialChangesetPlugin TracMercurialChangesetPlugin] to generate repository cache. 21 22 For mercurial backend, since [http://trac.edgewall.org/ticket/8417 TracMecurial did not support repository cache] yet, you should install [http://github.com/maraujop/TracMercurialChangesetPlugin TracMercurialChangesetPlugin] to generate the repository cache. 22 23 23 24 === Git 24 For git backend, according to #7746, you should add following config to git section: 25 26 For git backend, according to #7746, you should add following config to git section in the `trac.ini` file: 25 27 {{{#!ini 26 28 [git] … … 28 30 persistent_cache = true 29 31 }}} 32 30 33 You might need to run `trac-admin repository resync` after the change. 31 34 … … 56 59 You can check out TracTicketChangelogPlugin from [http://trac-hacks.org/svn/tracticketchangelogplugin here] using Subversion, or [source:tracticketchangelogplugin browse the source] with Trac. 57 60 58 == Install 61 == Installation 62 59 63 You can install this plugin following the standard procedures described in [wiki:TracPlugins#InstallingaTracplugin]. 60 64 … … 62 66 1. Change to the directory containning setup.py. 63 67 * (Optional): If you are using Trac 0.12 with i18n, you should compile language files here: 64 68 {{{#!sh 65 69 python setup.py compile_catalog -f 66 70 }}} … … 73 77 cp dist/*.egg /srv/trac/env/plugins 74 78 }}} 75 1. Config trac.ini:76 79 1. Add the following to the `trac.ini` file in the components section: 80 {{{#!ini 77 81 [components] 78 82 ticketlog.* = enabled … … 86 90 87 91 === Usage 88 * make sure you add `TICKETLOG_VIEW` permission to users 89 * you can config log_pattern to define your pattern.[[br]] 92 93 * Make sure you add `TICKETLOG_VIEW` permission to users. 94 * You can configure the log_pattern to define your pattern:[[br]] 90 95 `%s` in the pattern will be replaced with the referenced ticket number (e.g. 12345), so `\s*#%s+\s+.*` will be evaluated as `\s*#12345+\s+.*`. 91 96