Changes between Version 2 and Version 3 of TracRepositoryAdmin


Ignore:
Timestamp:
Oct 8, 2012, 7:07:27 PM (12 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • TracRepositoryAdmin

    v2 v3  
    77 * Set up a call to `trac-admin $ENV changeset added $REPO $REV` in the post-commit hook of each repository. Additionally, add a call to `trac-admin $ENV changeset modified $REPO $REV` in the post-revprop-change hook of repositories allowing revision property changes.
    88 * Set the `[trac] repository_sync_per_request` option to an empty value to disable per-request syncing.
    9 
     9 * Make sure the user under which your Subversion hooks are run has write access to the Trac environment, or use a tool like `sudo` to temporarily elevate privileges.
    1010
    1111== Specifying repositories == #Repositories
    … …  
    2424||The `dir` attribute specifies the location of the repository in the filesystem. It corresponds to the value previously specified in the option `[trac] repository_dir`. The `alias` and `dir` attributes are mutually exclusive. ||
    2525||`hidden` ||When set to `true`, the repository is hidden from the repository index page in the source browser. Browsing the repository is still possible, and links referencing the repository remain valid. ||
    26 ||`name` ||The `name` attribute specifies the leading path element to the repository. ||
    2726||`type` ||The `type` attribute sets the type of version control system used by the repository. Trac supports Subversion out-of-the-box, and plugins add support for many other systems. If `type` is not specified, it defaults to the value of the `[trac] repository_type` option. ||
    2827||`url` ||The `url` attribute specifies the root URL to be used for checking out from the repository. When specified, a "Repository URL" link is added to the context navigation links in the source browser, that can be copied into the tool used for creating the working copy. ||
    2928
    30 The `name` attribute and one of `alias` or `dir` are mandatory. All others are optional.
     29A repository `name` and one of `alias` or `dir` attributes are mandatory. All others are optional.
    3130
    3231After adding a repository, the cache for that repository must be re-synchronized once with the `trac-admin $ENV repository resync` command.
    … …  
    4140The main advantage of specifying repositories in `trac.ini` is that they can be inherited from a global configuration (see the [wiki:TracIni#GlobalConfiguration global configuration] section of TracIni). One drawback is that, due to limitations in the `ConfigParser` class used to parse `trac.ini`, the repository name is always all-lowercase.
    4241
    43 The following example defines two Subversion repositories named `project` and `lib`, and a hidden alias to `project` as the default repository. This is a typical use case where a Trac environment previously had a single repository (the `project` repository), and was converted to multiple repositories. The alias ensures that links predating the change continue to resolve to the `project` repository.
     42The following example defines two Subversion repositories named `project` and `lib`, and an alias to `project` as the default repository. This is a typical use case where a Trac environment previously had a single repository (the `project` repository), and was converted to multiple repositories. The alias ensures that links predating the change continue to resolve to the `project` repository.
    4443{{{
    4544#!ini
    … …  
    4948project.type = svn
    5049project.url = http://example.com/svn/project
     50project.hidden = true
     51
    5152lib.dir = /var/repos/lib
    5253lib.description = This is the secondary library code.
    5354lib.type = svn
    5455lib.url = http://example.com/svn/lib
     56
    5557.alias = project
    56 .hidden = true
    5758}}}
    5859Note that `name.alias = target` makes `name` an alias for the `target` repo, not the other way around.
    … …  
    107108/usr/bin/trac-admin /path/to/env changeset added "$1" "$2"
    108109}}}
     110Note: Ubuntu doesn't seem to like /usr/bin/trac-admin, so just use:
     111{{{#!sh
     112#!/bin/sh
     113export PYTHON_EGG_CACHE="/path/to/dir"
     114trac-admin /path/to/env/ changeset added "$1" "$2"
     115}}}
    109116On Windows (`post-commit.cmd`):
    110117{{{#!application/x-dos-batch
    … …  
    127134Note that calling `trac-admin` in your Subversion hooks can slow down the commit and log editing operations on the client side. You might want to use the [trac:source:trunk/contrib/trac-svn-hook contrib/trac-svn-hook] script which starts `trac-admin` in an asynchronous way. The script also comes with a number of safety checks and usage advices which should make it easier to set up and test your hooks. There's no equivalent `trac-svn-hook.bat` for Windows yet, but the script can be run by Cygwin's bash.
    128135
    129 See the [http://svnbook.red-bean.com/en/1.5/svn.reposadmin.create.html#svn.reposadmin.create.hooks section about hooks] in the Subversion book for more information. Other repository types will require different hook setups. Please see the plugin documentation for specific instructions.
     136See the [http://svnbook.red-bean.com/en/1.5/svn.reposadmin.create.html#svn.reposadmin.create.hooks section about hooks] in the Subversion book for more information. Other repository types will require different hook setups.
     137
     138Git hooks can be used in the same way for explicit syncing of git repositories. Add the following to `.git/hooks/post-commit`:
     139{{{#!sh
     140REV=$(git rev-parse HEAD)
     141trac-admin /path/to/env changeset added <my-repository> $REV
     142}}}
     143
     144For Mercurial, add the following entries to the `.hgrc` file of each repository accessed by Trac (if [trac:TracMercurial] is installed in a Trac `plugins` directory, download [trac:source:mercurial-plugin/tracext/hg/hooks.py hooks.py] and place it somewhere accessible):
     145{{{#!ini
     146[hooks]
     147; If mercurial-plugin is installed globally
     148commit = python:tracext.hg.hooks.add_changesets
     149changegroup = python:tracext.hg.hooks.add_changesets
     150
     151; If mercurial-plugin is installed in a Trac plugins directory
     152commit = python:/path/to/hooks.py:add_changesets
     153changegroup = python:/path/to/hooks.py:add_changesets
     154
     155[trac]
     156env = /path/to/env
     157trac-admin = /path/to/trac-admin
     158}}}
    130159
    131160=== Per-request synchronization === #PerRequestSync
    … …  
    139168
    140169 1. Remove the default repository specification from the `[trac] repository_dir` option.
    141  1. Add the "main" repository as a named repository.
     170 1. Add the main repository as a named repository.
    142171 1. Re-synchronize the main repository.
    143  1. Set up post-commit and post-revprop-change hooks on the main repository, and set `[trac] repository_sync_per_request` to an empty value.
    144  1. Add a hidden alias to the main repository as the default repository. This ensures that all links predating the migration still resolve to the main repository.
    145  1. Repeat steps 2, 3 and 4 to add other (named) repositories as needed.
     172 1. Set up post-commit and post-revprop-change hooks on the "main" repository, and set `[trac] repository_sync_per_request` to an empty value.
     173 1. Add an alias to the main repository as the default repository (by leaving out the the `name`, e.g. `.alias = main`). This ensures that all links predating the migration still resolve to the main repository.
     174 1. Repeat steps 2, 3 and 4 to add other "named" repositories as needed.
    146175
    147176== Migration from a single-repository setup (Mercurial) == #MigrationMercurial
    148 The following procedure illustrates a typical migration from a Mercurial single-repository setup to multiple repositories. Please note that at the time of writing, no initial resynchronization or any hooks are necessary for Mercurial repositories - see #9485 for more information.
     177The following procedure illustrates a typical migration from a Mercurial single-repository setup to multiple repositories. Please note that at the time of writing, no initial resynchronization or any hooks are necessary for Mercurial repositories - see [trac:ticket:9485 #9485] for more information.
    149178
    150179 1. Upgrade to the latest version of the TracMercurial plugin.
    151180 1. Remove the default repository specification from the `[trac] repository_dir` option.
    152  1. Add the "main" repository as a named repository.
    153  1. Add a hidden alias to the main repository as the default repository. This ensures that all links predating the migration still resolve to the main repository.
    154  1. Repeat step 3 to add other (named) repositories as needed.
     181 1. Add the main repository as a named repository.
     182 1. Add an alias to the main repository as the default repository (by leaving out the the `name`, e.g. `.alias = main`). This ensures that all links predating the migration still resolve to the main repository.
     183 1. Repeat step 3 to add other "named" repositories as needed.
    155184
    156185== Troubleshooting ==