Changes between Version 2 and Version 3 of TracRepositoryAdmin
- Timestamp:
- Apr 16, 2016, 7:07:21 PM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracRepositoryAdmin
v2 v3 79 79 Note that the default repository has an empty name, so it will likely need to be quoted when running `trac-admin` from a shell. Alternatively, the name "`(default)`" can be used instead, for example when running `trac-admin` in interactive mode. 80 80 81 == Repository caching 82 83 The Subversion and Git repository connectors support caching, which improves the performance browsing the repository, viewing logs and viewing changesets. Cached repositories must be [#Synchronization synchronized]; either explicit or implicit synchronization can be used. When searching changesets, only cached repositories are searched. 84 85 Subversion repositories are cached unless the type is `direct-svnfs`. Git repositories are cached when `[git]` [wiki:TracIni#git-section cached_repository] is `true`. 81 86 82 87 == Repository synchronization #Synchronization … … 144 149 {{{#!sh 145 150 #!/bin/sh 151 tracenv=/path/to/env # change with your Trac environment's path 152 repos= # change with your repository's name 146 153 while read oldrev newrev refname; do 147 git rev-list --reverse $newrev ^$oldrev | \ 148 while read rev; do 149 trac-admin /path/to/env changeset added <repos> $rev 150 done 154 if [ "$oldrev" = 0000000000000000000000000000000000000000 ]; then 155 git rev-list --reverse "$newrev" -- 156 else 157 git rev-list --reverse "$newrev" "^$oldrev" -- 158 fi | xargs trac-admin "$tracenv" changeset added "$repos" 151 159 done 152 160 }}} … … 178 186 179 187 188 == Automatic changeset references in tickets 189 190 You can automatically add a reference to the changeset as a ticket comment whenever changes are committed to the repository. The description of the commit needs to contain one of the following formulas: 191 * '''`Refs #123`''' - to reference this changeset in `#123` ticket 192 * '''`Fixes #123`''' - to reference this changeset and close `#123` ticket with the default status ''fixed'' 193 194 This functionality requires installing a post-commit hook as described in [#ExplicitSync], and enabling the optional commit updater components by adding the following line to the `[components]` section of your [wiki:TracIni#components-section trac.ini], or enabling the components in the //Plugins// admin panel. 195 {{{#!ini 196 tracopt.ticket.commit_updater.* = enabled 197 }}} 198 For more information, see the documentation of the `CommitTicketUpdater` component in the //Plugins// admin panel and the [trac:CommitTicketUpdater] page. 199 180 200 == Migration from a single-repository setup (Subversion) #Migration 181 201 The following procedure illustrates a typical migration from a Subversion single-repository setup to multiple repositories.
