devZing Support

Manage Hooks (7 of 7): MantisBT Integration

justin — Fri, 06 Jan 2012 20:00:33 +0000

Now MantisBT and Subversion have their chance to meet.

This hook is similar to Bugzilla integration. It connects your Subversion to the bug tracker MantisBT.

Please contact support if you’d like this feature enabled.

Manage Hooks (1 of 7): Starting the Process

justin — Fri, 06 Jan 2012 20:00:11 +0000

Once you have created your devZing Subversion hosting account and have created your repositories, you will want to configure the hooks. Here are the first steps to take for each hook.

Begin by logging into your account. https://devzing.com/login

Click “Manage Repositories”.

Manage Repositories

The option to configure “Hooks” shows up on the same page your repositories are listed.

Configure Hooks

Click “configure” under the “Hooks” column.

Click "Configure"

Now move on to configure each hook…

Require commit message

Email on commit

GET on commit (webhook)

Change commit messages

Bugzilla integration

MantisBT integration

Manage Hooks (2 of 7): Require Commit Message

justin — Fri, 06 Jan 2012 19:59:49 +0000

The first hook to configure is the Require Commit Message.

Subversion users “commit” to the repository. With this hook you can require your commiters to put in a comment with each commit. When they don’t put in a comment, your message will show up announcing a commit failure. Yes, the commit will fail.

Go to: Initial Hook Configuration Instructions

You’ll see this field:

Require Commit Message

In the “Require Commit Message” field, enter the message you want to show up.Note: If you leave the field blank, no message will show up.

So just think of what you’d like your commiters to see when they don’t enter a comment on a commit.

Manage Hooks (3 of 7): Email On Commit

justin — Fri, 06 Jan 2012 19:59:29 +0000

When a commit is successful, you may want emails sent saying so. If this is the case, enter them in this field, each separated by a comma.

Go to: Initial Hook Configuration Instructions

Then:

Email On Commit

Enter the email addresses, each separated with a comma.

The email will display the name of the committing user and list all the paths that were changed. It will also list the “svn update-style” status letters in the first two columns.

Manage Hooks (4 of 7): GET on commit (webhook)

justin — Fri, 06 Jan 2012 19:59:09 +0000

You can start a build server or any other process you have set up when you commit in Subversion. If you want to start this process automatically whenever you commit, use this hook.

You will need to know the appropriate URL on your server to start your custom process.

Go to: Initial hook configuration instructions

GET on commit (webhook)

The hook will access this URL whenever you commit.

Manage Hooks (6 of 7): Enable Bugzilla Integration

justin — Fri, 06 Jan 2012 19:58:14 +0000

Bugzilla and Subversion meet here. You can tie Subversion commits to bugs in Bugzilla. It’s as easy as checking the box.

Go to: Initial Hook Configuration Instructions

Bugzilla Integration

Which bug number does the commit fix? The hook looks up the Bugzilla bug(s) specified in the commit message and adds the commit message as a comment to the bug.

…So just check the box if you want your Subversion hook integrated with Bugzilla.

Manage Hooks (5 of 7): Change Commit Messages

justin — Fri, 06 Jan 2012 19:57:34 +0000

If you ever need to change a commit message use this hook.

Initial hook configuration instructions

Just check the box to allow the messages to be changed then you can use the propedit or propset subcommands to correct the commit messages.

Be sure to turn this hook off again after you’re done unless you want anybody to be able to edit commit messages.

devZing Subversion: Delete a Repository

justin — Fri, 16 Dec 2011 00:29:05 +0000

So you created a repository. But now you need to delete. How in the world do I delete a Subversion repository? Here you go…

Manage Repositories

Log into your devZing account (https://devzing.com/login). Click “Manage Repositories”.

List of Repositories

Look at your list of repositories, skim down to “Delete”.

Find "Delete"

Click “Delete” for the repository you want to delete.You’ll see this:

Click "Delete"

Click “Delete”. You’re good to go. Note that deleting a repository is permanent.

Subversion: Get Hooked On It

justin — Mon, 05 Dec 2011 21:16:06 +0000

devZing subversion hosting offers an excellent enhancement to your Subversion workflow through hook scripts. We offer you several options to get exactly what you need from the process.

Here are the hooks we give you:

Require commit message - This hook requires your commiters to provide a comment with each commit. If they don’t provide one, the message you specify will be displayed and the commit will be rejected.
Email on commit - Did you ever want to know that someone committed something to your repository without you having to check every 5 minutes? This hook will email you every time a commit happens.
GET on commit (webhook) - This hook will access a specific URL each time there is a commit. This causes your system to do something like an automatic build.
Change commit messages - If you’ve ever specified the wrong commit message you’ll appreciate this hook. It allows you to correct the commit messages using the propedit or propset subcommands.
Bugzilla integration - This hook allows you to tie your subversion commits to bugs in your Bugzilla. Just specify the bug numbers the commit fixes and the hook will add the comment message to each bug (as a comment).
MantisBT integration - Similar to Bugzilla integration; however, this hook is enabled from within MantisBT.

How Do I Create Subversion Backups

justin — Mon, 05 Dec 2011 21:14:50 +0000

How do I create a backup of my devZing hosted subversion repository?

devZing automatically keeps several days of backups for you at multiple off-site locations. However, if you ever want to have a backup copy on your own computer here is how you would go about it.

Click Manage Repositories,

You will see a list of your repositories:

List of Repositories

Find the Backup column, down the line of the repository you want to create a backup for.

Click create.

Click Create

Your backed up repository will appear under “Repository Backups”. At first, the Status will say “pending”.

Once the backup has processed, though, it will say “Complete”.

It will say "Complete"

Click the download link and the backup will be copied to your computer.

That’s the process. It’s a simple task, but important.