Changes between Version 22 and Version 23 of RepositoryHookSystemPlugin


Ignore:
Timestamp:
Nov 11, 2015, 4:24:20 PM (8 years ago)
Author:
figaro
Comment:

Replace download with export, add generic installation instructions

Legend:

Unmodified
Added
Removed
Modified
  • RepositoryHookSystemPlugin

    v22 v23  
    1919 * plugins can be enabled on a per-hook basis
    2020
    21  * 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.
     21 * 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.
    2222
    23  * 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. A changeset object can be faked if it is not available (like it is at SVN post-commit).
     23 * 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. A changeset object can be faked if it is not available (like it is at SVN post-commit).
    2424
    2525 * the logic of the !RepositoryChangeListeners is agnostic to SCM type and hook used.
     
    3535 * arbitrary hooks, not just post-commit
    3636
    37 However, while architected to be arbitrary, this plugin has only been implemented for SVN.
     37However, while architected to be generic, this plugin has only been implemented for SVN.
    3838
    3939== Bugs/Feature Requests
    4040
    41 If you are getting an error about `PYTHON_EGG_CACHE` not being set, then you may need to set this in your hook.  See TracPlugins#Abouthookscripts
     41If you are getting an error about `PYTHON_EGG_CACHE` not being set, then you may need to set this in your hook. See TracPlugins#Abouthookscripts.
    4242
    4343Existing bugs and feature requests for RepositoryHookSystemPlugin are
     
    4646If you have any issues, create a
    4747[/newticket?component=RepositoryHookSystemPlugin new ticket].
    48 If you want to submit patches, please read the
    49 [wiki:olemis#Guidelinestocollaborate patch submission guidelines].
    5048
    5149[[TicketQuery(component=RepositoryHookSystemPlugin&group=type,format=progress)]]
     
    5351== Download
    5452
    55 Download the zipped source from [download:repositoryhooksystemplugin here].
     53Download the zipped source from [export:repositoryhooksystemplugin here].
    5654
    5755== Source
    5856
    5957You can check out RepositoryHookSystemPlugin from [/svn/repositoryhooksystemplugin here] using Subversion, or [source:repositoryhooksystemplugin browse the source] with Trac.
     58
     59== Installation
     60
     61General instructions on installing Trac plugins can be found on the [TracPlugins#InstallingaTracplugin TracPlugins] page.
    6062
    6163== Example