Changes between Version 15 and Version 16 of BitbucketSyncPlugin
- Timestamp:
- Mar 24, 2017, 6:40:53 PM (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
BitbucketSyncPlugin
v15 v16 11 11 After installation of this plugin, you have to configure Bitbucket to notify Trac about changes. You do this on Bitbucket under ''Admin'' -> ''Services'' section, where you select ''POST'' service type and enter an URL of your Trac installation's `/bitbucketsync` handler. For example, if your Trac installation is on `http://www.example.com/`, then enter `http://www.example.com/bitbucketsync` as service URL. 12 12 13 Name of the repository on Bitbucket should match (it is case sensitive) the local one (you can use aliases in Trac 0.12 to assure that). User under which Trac is running on the server should have write access to the local repository for which it is configured and you want to sync.13 The name of the repository on Bitbucket should match the local one, and it is case sensitive. You can use aliases in Trac 0.12 to ensure that. The user under which Trac is running on the server should have write access to the local repository for which it is configured and you want to sync. 14 14 15 Of course, local repository should be properly configured into Trac (commit and incoming hooks configured and so on). Then also ticket updates through commit messages is possible.15 Of course, the local repository should be properly configured into Trac (commit and incoming hooks configured and so on). Then also ticket updates through commit messages is possible. 16 16 17 17 == Bugs/Feature Requests