Anonymous Access

Anonymous access is now available to all myVersionControl customers on both Subversion and Trac. This is a feature that has been regularly requested by clients and we are very pleased to be able to offer it in the new version of myVersionControl.

Anonymous access to Subversion repositories when activated means that you can now permit public users to browse your code directly without being prompted for a username or password.
In Trac your users will again not be prompted and the system assumes a default user of "Anon". Anonymous privileges in Trac are completely configurable by Administrators so you can make your Trac as open or secure as you wish.

Of course you can choose not to permit anonymous access. The security area in your control panel makes it very easy to configure your resources:

New and improved Trac comes to myVersionControl

Trac was a superb and popular base level project management tool in the previous incarnation of myVersionControl so we have included trac across our new product range at no extra cost.

We have put alot of hard work improving the management of Trac compared to the old version:



Version 0.11.4 - The latest version with all the current features.
Webadmin - Installed by default on all Trac instances.
Control panel - A once click deployment model and management through the control panel.
Administrators - myVersionControl administrators are automatically Trac administrators.
Subversion - Log messages can be used to automatically update Trac.

This is available to all our users now, it is configurable like never before an will take less than 30 seconds to install! In your control panel, navigate to the 'Resources and Hooks' section and choose 'Trac'.

Depending on your needs there are better things out there but they invariably cost money. We are adding support for all the other popular ticket and project management sites out there and will add these features shortly. If you would like to make a suggestion please start a discussion at http://support.myversioncontrol.com

Controlling commit messages

We released our 'commit message' feature today and are looking forward to any comments you may have.

This feature is available to all our paid accounts and gives administrators far more control over what is acceptable in a log message.

Prevent zero length commits -
No more blank messages in your log! Always always always log your changes! At myVersionControl we like to commit tested functionality in small identifiable blocks. Preaching to the converted I am sure but write your log message while the code is fresh in your mind - the more the better! You will never regret it..

Along with zero length commits we have provided the ability to set minimum lengths of log message. This means that your users cannot get away with just a single character (yes we have seen it!) to bypass the control.

Finally, we have given the option of creating your own custom message. You can put anything you like in there - your support telephone number, the name of the business or just something cheeky! It is up to you!

Gmail filters for your email notifications

The new email notification functions in myVersionControl have just been implimented and all of a sudden the filters in my Gmail account have stopped working. The reason is obvious. Instead of coming from no-reply@myversioncontrol.com, email notifications now come from the user that triggered them. As such, I'm going to have to look for another constant to identify and label these emails with.

Ok - here's what I did, the subject line of all email notifications will look something like this:

Project [projectname] commit r[revision number] - [folder path]

Google lets you group words which must appear together using parentheses, so you can add (project commit) to the Subject field of the Create a Filter page. If you want to make the filter project specific, just add the project name within the brackets too (project coolproject commit).

Email Notifications now live

After our major upgrade in August, we had to disable our hooks and resources section. We're now ready to start releasing features here one by one over the next few days. The first one is email notifications.

When activated, Email Notifications will send an email to users or groups that you specify whenever someone commits to a specified project. We've added in a couple of neat features:

Email to all members of a group
If you've gone to the trouble of setting up groups to make managing user permissions easier, then you'll be pleased to know that you you can manage email rules using these groups.

Temporarily disable Email Notifications
If you need to switch off email notifications for a project for a while, then you can. When you come to re-enable notifications again, all your previous settings are remembered and ready to go.

Notifications come from the user
When a team member commits their code, and I want to ping them a comment via email, it would be nice just to hit reply rather having to hit forward and look up their email address. Well now rather than coming from no-reply@myVersionControl.com, the notification email will come with from the user who committed the change. It wasn't difficult to implement, but it's just a nice little addition that makes our lives that wee bit easier.