Changes between Version 1 and Version 2 of TracRepositoryAdmin
- Timestamp:
- May 31, 2020, 9:49:25 PM (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracRepositoryAdmin
v1 v2 24 24 ||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. || 25 25 ||`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 ||`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. ||26 ||`type` ||The `type` attribute sets the type of version control system used by the repository. Trac supports Subversion and Git 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. || 27 27 ||`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. || 28 28 … … 90 90 91 91 === 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-changehook as well.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. 93 93 94 94 `changeset added <repos> <rev> [...]`:: … … 100 100 The `<repos>` argument can be either a repository name (use "`(default)`" for the default repository) or the path to the repository. 101 101 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. 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. 103 104 ==== Subversion ==== 103 105 104 106 The 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`): … … 108 110 /usr/bin/trac-admin /path/to/env changeset added "$1" "$2" 109 111 }}} 112 Note: Check with `whereis trac-admin`, whether `trac-admin` is really installed under `/usr/bin/` or maybe under `/usr/local/bin/` and adapt the path. 110 113 On Windows (`post-commit.cmd`): 111 {{{#! application/x-dos-batch114 {{{#!bat 112 115 @C:\Python26\Scripts\trac-admin.exe C:\path\to\env changeset added "%1" "%2" 113 116 }}} … … 120 123 }}} 121 124 On Windows (`post-revprop-change.cmd`): 122 {{{#! application/x-dos-batch125 {{{#!bat 123 126 @C:\Python26\Scripts\trac-admin.exe C:\path\to\env changeset modified "%1" "%2" 124 127 }}} … … 130 133 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. 131 134 132 Git hooks can be used in the same way for explicit syncing of git repositories. Add the following to `.git/hooks/post-commit`: 133 {{{#!sh 134 REV=$(git rev-parse HEAD) 135 trac-admin /path/to/env changeset added <my-repository> $REV 136 }}} 137 138 For 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 [source:plugins/0.13/mercurial-plugin/tracext/hg/hooks.py hooks.py] and place it somewhere accessible): 135 ==== Git ==== 136 137 Git 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 140 REV=$(git rev-parse HEAD) 141 trac-admin /path/to/env changeset added <repos> $REV 142 }}} 143 144 Alternately, 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 147 while 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 152 done 153 }}} 154 155 The `<repos>` argument can be either a repository name (use "`(default)`" for the default repository) or the path to the repository. 156 157 ==== Mercurial ==== 158 159 For 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): 139 160 {{{#!ini 140 161 [hooks] … … 169 190 170 191 == Migration from a single-repository setup (Mercurial) == #MigrationMercurial 171 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 #9485for more information.192 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 [trac:ticket:9485 #9485] for more information. 172 193 173 194 1. Upgrade to the latest version of the TracMercurial plugin.
