After creating a repository you will need to create users and grant permissions to them so they can access the repository. To create a user go to https://secure.devzing.com/subversion and look for the green “Add User” button near the bottom of the page. After creating the user they will be listed underneath the list of repositories. […]
Category: Subversion
Hooks(8)
Trac: Associate New Trac Project with Existing Subversion Repository
To associate a new Trac project with an existing Subversion repository: Create a Trac project with exactly the same name as the Subversion repository Then assign yourself TRAC_ADMIN permissions (so you can manage the Trac project) Finally resync the Trac project to bring in all the changesets from Subversion
Subversion: Allow Property Changes
Some tools such at replication need the ability to change various subversion properties. By default subversion does not allow this because it is not a tracked change. You may be told that the “pre-reveprop-change” hook needs to be created or something similar. To allow this choose Property changes from the Action menu of the repository. […]
Subversion: Email on Commit
A very typical workflow is to notify a list of individuals via email every time a commit is performed. To do this choose Email on commit from the Action menu. Enter a list of comma separated emails to be notified and click Change.
Subversion: Require a Commit Message
To require your users to supply a commit message choose Require commit message from the Action menu of the repository. Enter a message to be displayed to the users if they don’t provide a commit message and click Change.
Subversion: Bugzilla Integration
You can now have every subversion commit message added to specific Bugzilla issues. You do this by specifying the bug number in the commit message with the word “bug” or “issue” just before it. For example: This commit fixes issue 145 by fixing the CSS. The integration will look up Bugzilla issue 145 and add a […]
Subversion: JIRA Integration
You can now have every subversion commit message added to specific JIRA issues. You do this by specifying the project ID and the issue number in the commit message with the word “bug” or “issue” just before it. For example: This commit fixes issue PROJ1-145 by fixing the CSS. The integration will look up JIRA […]
API: Subversion Backup
This API allows you to programmatically initiate a backup of all of your Subversion repositories. The URL for the API calls is: https://secure.devzing.com/api/v1/subversion/backup?apikey={key} You can find your key in Settings -> Account info. Note that these API calls place a request for a backup onto a queue and return immediately. You will receive an email […]
Subversion: Slack Integration
You can now have every subversion commit be sent to a Slack channel. Here is how to get started: First enable the Subversion integration in Slack. Go to <yourslack>.slack.com/services/new/subversion Create or choose a channel where commits will be posted Copy the Token Click Save Integration Go to https://devzing.com/login Click the Subversion menu Click Action for the repository you […]
Subversion: Update works, but commit fails
“I’m getting the error message Authorization failed when trying to commit my subversion changes. What is wrong?” We get this question from time to time Turns out there is a quirk in Subversion where you can use a URL for checkout or update, but won’t work for a commit. The checkout allows the case of […]