Changes between Version 3 and Version 4 of Trac Repository Admin


Ignore:
Timestamp:
Dec 10, 2014, 10:01:01 PM (10 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Trac Repository Admin

    v3 v4  
    9090
    9191=== Explicit synchronization === #ExplicitSync
    92 This is the preferred method of repository synchronization. It requires setting the `[trac]  repository_sync_per_request` option in [wiki:TracIni#trac-section trac.ini] to an empty value, and adding a call to `trac-admin` in the post-commit hook of each repository. Additionally, if a repository allows changing revision metadata, a call to `trac-admin` must be added to the post-revprop-change hook as well.
     92This is the preferred method of repository synchronization. It requires setting the `[trac]  repository_sync_per_request` option in [wiki:TracIni#trac-section trac.ini] to an empty value, and adding a call to `trac-admin` in the `post-commit` hook of each repository. Additionally, if a repository allows changing revision metadata, a call to `trac-admin` must be added to the `post-revprop-change` hook as well.
    9393
    9494 `changeset added <repos> <rev> [...]`::
    … …  
    100100The `<repos>` argument can be either a repository name (use "`(default)`" for the default repository) or the path to the repository.
    101101
    102 Note that you may have to set the environment variable PYTHON_EGG_CACHE to the same value as was used for the web server configuration before calling trac-admin, if you changed it from its default location. See [wiki:TracPlugins Trac Plugins] for more information.
     102Note that you may have to set the environment variable `PYTHON_EGG_CACHE` to the same value as was used for the web server configuration before calling `trac-admin`, if you changed it from its default location. See [wiki:TracPlugins Trac Plugins] for more information.
     103
     104==== Subversion ====
    103105
    104106The following examples are complete post-commit and post-revprop-change scripts for Subversion. They should be edited for the specific environment, marked executable (where applicable) and placed in the `hooks` directory of each repository. On Unix (`post-commit`):
    … …  
    108110/usr/bin/trac-admin /path/to/env changeset added "$1" "$2"
    109111}}}
    110 Note: Ubuntu doesn't seem to like /usr/bin/trac-admin, so just use:
    111 {{{#!sh
    112 #!/bin/sh
    113 export PYTHON_EGG_CACHE="/path/to/dir"
    114 trac-admin /path/to/env/ changeset added "$1" "$2"
    115 }}}
     112Note: Check with `whereis trac-admin`, whether `trac-admin` is really installed under `/usr/bin/` or maybe under `/usr/local/bin/` and adapt the path.
    116113On Windows (`post-commit.cmd`):
    117 {{{#!application/x-dos-batch
     114{{{#!bat
    118115@C:\Python26\Scripts\trac-admin.exe C:\path\to\env changeset added "%1" "%2"
    119116}}}
    … …  
    126123}}}
    127124On Windows (`post-revprop-change.cmd`):
    128 {{{#!application/x-dos-batch
     125{{{#!bat
    129126@C:\Python26\Scripts\trac-admin.exe C:\path\to\env changeset modified "%1" "%2"
    130127}}}
    … …  
    136133See 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.
    137134
    138 Git hooks can be used in the same way for explicit syncing of git repositories. Add the following to `.git/hooks/post-commit`:
    139 {{{#!sh
    140 REV=$(git rev-parse HEAD)
    141 trac-admin /path/to/env changeset added <my-repository> $REV
    142 }}}
     135==== Git ====
     136
     137Git hooks can be used in the same way for explicit syncing of Git repositories.  If your git repository is one that gets committed to directly on the machine that hosts trac, add the following to the `hooks/post-receive` file in your git repo (note: this will do nothing if you only update the repo by pushing to it):
     138{{{#!sh
     139#!/bin/sh
     140REV=$(git rev-parse HEAD)
     141trac-admin /path/to/env changeset added <repos> $REV
     142}}}
     143
     144Alternately, if your repository is one that only gets pushed to, add the following to the `hooks/post-receive` file in the repo:
     145{{{#!sh
     146#!/bin/sh
     147while read oldrev newrev refname; do
     148        git rev-list --reverse $newrev ^$oldrev  | \
     149        while read rev; do
     150                trac-admin /path/to/env changeset added <repos> $rev
     151        done
     152done
     153}}}
     154
     155The `<repos>` argument can be either a repository name (use "`(default)`" for the default repository) or the path to the repository.
     156
     157==== Mercurial ====
    143158
    144159For 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):