Changes between Version 3 and Version 4 of RepositoryHookSystemPlugin
- Timestamp:
- Sep 9, 2008, 2:08:35 PM (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
RepositoryHookSystemPlugin
v3 v4 1 1 = turn repository hooks into pluggable extension points = 2 2 3 '''This plugin has only been tested with SVN's post-commit hook. Additional work may be required to get this to work with other SCMs and other SVN hooks. Please contact the [wiki:k0s author] or [http://trac-hacks.org/newticket?component=RepositoryHookSystemPlugin&owner=k0s open a ticket] if you need additional functionality for this plugin (contributors also welcome).''' If you're looking for existing plugins that work with SVN hooks,try the SvnChangeListenerPlugin or the TracSvnPoliciesPlugin, or perhaps the contributed [trac:browser:trunk/contrib/trac-post-commit-hook trac post-commit hook] is sufficient for your purposes.3 '''This plugin has only been tested with SVN's post-commit hook. Additional work may be required to get this to work with other SCMs or other SVN hooks. Please contact the [wiki:k0s author] or [http://trac-hacks.org/newticket?component=RepositoryHookSystemPlugin&owner=k0s open a ticket] if you need additional functionality for this plugin (contributors also welcome).''' If you're looking for plugins that work with SVN hooks, you might also try the SvnChangeListenerPlugin or the TracSvnPoliciesPlugin, or perhaps the contributed [trac:browser:trunk/contrib/trac-post-commit-hook trac post-commit hook] is sufficient for your purposes. 4 4 5 5 == Description == … … 11 11 * the RepositoryHookSystemPlugin is able to enable and disable its presence in the SVN hooks directory without affecting other plugins 12 12 13 * the trac-post-commit-hook has been converted to a configurable plugin that does ticket changes (see {{{ticketchanger.py}}})13 * the trac-post-commit-hook has been converted to a configurable plugin that does ticket changes (see source:repositoryhooksystemplugin/0.11/repository_hook_system/ticketchanger.py) 14 14 15 15 * has a webadmin interface for configuring hooks including figuring out whether or not the plugin has been enabled on a per-project basis … … 19 19 * the listeners are invoked via a command-line call from one of the repository hooks. This is a one-line command that passes whatever details are necessary to identify the changeset. 20 20 21 * a trac changeset object is used to pass around information. This is good, as it avoids unneccessary information to be sought by the !RepositoryChangeListeners. For the SvnChangeListenerPlugin (at least as it stands living only in the post-commit -hook), this is sufficient. It is unknown whether this is a good idea for other hooks and repository systems. If a unified interface for a changeset object were available, then a changeset object could be "fakeable" if its not available (like it is at SVN post-commit). If not, this is a big conceptual hole. ''To be investigated.''21 * a trac changeset object is used to pass around information. This is good, as it avoids unneccessary information to be sought by the !RepositoryChangeListeners. For the SvnChangeListenerPlugin (at least as it stands living only in the post-commit hook), this is sufficient. It is unknown whether this is a good idea for other hooks and repository systems. If a unified interface for a changeset object were available, then a changeset object could be "fakeable" if its not available (like it is at SVN post-commit). If not, this is a big conceptual hole. ''To be investigated.'' 22 22 23 23 * the logic of the !RepositoryChangeListeners is agnostic to SCM type and hook used. … … 67 67 == Author/Contributors == 68 68 69 ''Originally developed at [http://topp.openplans.org The Open Planning Project]'' 70 69 71 '''Author:''' [wiki:k0s] [[BR]] 70 72 '''Contributors:'''
