Tag Archive for 'asf'

ASF Announces Apache Bloodhound as Top-Level Project

WANdisco submitted Bloodhound to the Apache Incubator in December 2011 and our developers have been involved in the Apache Bloodhound project since its inception. So we’re pleased that today the Apache Software Foundation (ASF) officially announced Bloodhound as a Top-Level Project (TLP).

Bloodhound is a Trac-based software development collaboration tool that includes an Apache Subversion repository browser, wiki, and defect tracker. It’s also compatible with the hundreds of free plugins available for Trac, allowing users to customize their experience even further.

WANdisco received many requests for an issue tracker and at the time, open source options available for integration were limited, which is why we decided to invest in setting one up in the Apache Incubator,” said David Richards, CEO of WANdisco. “WANdisco has been actively supportive of the ASF, and we’re proud to have played a leading role in Bloodhound.”

When Bloodhound entered the incubator, while it was built on the Trac framework, it was a completely new project,” said Gary Martin, Vice President of Apache Bloodhound and WANdisco developer. “Bloodhound’s strengths lie in its powerful combination of Apache Subversion source control and robust ticket system.”

You can learn more about Apache Bloodhound, and download the latest 0.5.2 release, at the Bloodhound website.


Happy Holidays from WANdisco!

wandisco-christmas-2012-blog (1)

2012 has been an amazing year for WANdisco: a successful flotation, a patent approval, two acquisitions, a global series of WANdisco-organized Subversion conferences and upgrading our sponsorship of the Apache Software Foundation were just some of the highlights of the past twelve months.

We have plenty of exciting announcements planned for 2013, but for now we’d just like to thank everyone who has used our products, joined us for a webinar, eTraining or enterprise training session, picked us for your support needs, or provided us with the crucial feedback we need to make our products and services even better.

And, of course, we’d like to wish you a very happy holidays from the WANdisco Team!

Apache Subversion 1.7.8 Released

It may be nearly the end of the year, but there’s still time for one more release of Apache Subversion. SVN 1.7.8 features plenty of fixes and enhancements, including:

  • Adding missing attributes to “svn log -v –xml” output
  • Fixing a hang that could occur during error processing
  • Fixing incorrect status returned by 1.6 API
  • Adding Vary: header to GET responses to improve cacheability
  • Subversion 1.7.8 ignores file externals with mergeinfo when merging

A full list of everything’s that new in Subversion 1.7.8 is available at the Changes file. Free binaries of Subversion 1.7.8 are available to download through the WANdisco website.

Looking for a cross-platform Subversion client? Claim your free 30 day trial of SmartSVN Professional by visiting www.smartsvn.com/download

Subversion Tip of the Week

Polling Subversion with Jenkins

There are many advantages Jenkins can offer Apache Subversion users, one of which is the option of automatically polling Subversion repositories for changes, and creating a new build whenever changes are detected. In this week’s tip, we’ll show you how to configure Jenkins to automatically poll an uberSVN repository.

(Note, this tutorial requires Jenkins to be installed in uberSVN. See Getting Started with Jenkins in uberSVN for a step-by-step guide to getting Jenkins up and running.)

1. Open the ‘Jenkins’ tab and select the ‘New Job’ option from the left-hand menu.

2. Enter a Name for your job and indicate whether you are wanting to Copy Existing Job. Click ‘Ok.’

3. You will be taken to the ‘Configure’ screen. Enter a description for your job and select ‘Subversion’ as the source code management option. You will then be asked to enter the URL of the repository you wish to link the job to.

4. Under ‘Build Triggers’ select ‘Poll SCM.’ In the ‘Schedule’ text box, enter how often you want Jenkins to poll the repository. You can specify the frequency that Jenkins will poll Subversion, using the following format:

MINUTE: Minutes within the hour (0-59)
HOUR: The hour of the day (0-23)
DOM: The day of the month (1-31)
MONTH: The month (1-12)
DOW: The day of the week (0-7) where 0 and 7 are Sunday.

@annually, @yearly, @monthly, @weekly, @daily, @midnight, and @hourly are also supported.

5. Click ‘Save’ and Jenkins will begin automatically polling your Subversion repository at the specified intervals.

Not yet started with uberSVN? It’s free to download and free to use. Visit http://www.ubersvn.com/ now to get started.

Subversion Tip of the Week

Advanced Subversion Polling with Jenkins

It’s common practice to work on different projects simultaneously, but with so much going on it’s easy to lose track of where files originated, and what version is being used by which project. Thankfully, Jenkins supports file fingerprinting, which allows you to see exactly when and where your files are being produced and used. Once you’ve configured a Jenkins job to poll Subversion, setting up file fingerprinting is made easy with uberSVN.

1. Select the ‘Jenkins’ tab, followed by the Jenkins job you previously setup to poll Subversion.

2. Select the ‘Configure’ option.

3. Select the ‘Record fingerprints of files to track usage’ option and specify which files to track in the ‘Files to fingerprint’ text box. In this example, trunk/*.zip will track all .zip files in the trunk.

5. Make some changes to the files earmarked for fingerprinting, and commit those changes as normal.

6. Open the build report in Jenkins and select ‘See Fingerprints.’

7. This screen will display some basic details about the tracked files. To drill down into the information on any file, select the ‘more details’ link.

uberSVN is free to download and free to use. Visit http://www.ubersvn.com/ now to download your copy.

Apache Bloodhound 0.2 Released

The Apache Bloodhound team recently announced the first release of this new project, and now we’re excited to see that the second release of Apache Bloodhound has arrived!

Apache Bloodhound 0.2 (Incubating) upgrades to Bootstrap version 2.1, and fixes various issues from the 0.1 release, alongside various bug fixes relating to the new user interface. See the Release Notes for more information on what’s new in this release.

Apache Bloodhound (Incubating) is a software collaboration tool based on the code base of Trac, the proven project management and issue tracking system. Bloodhound will include issue tracking, a wiki, and repository browsing.

Although WANdisco are sponsoring some of the initial committers, one of the Apache Bloodhound project’s core goals is to create a strong developer community around the Trac code base in a vendor-neutral location. If you’re interested in participating in the Apache Bloodhound project, we invite you to review the information available at the ‘Getting Involved With Apache Bloodhound’ page.

Congratulations to the Apache Bloodhound team on another great release!

How to Create a Branch and Tag in Apache Subversion

In Apache Subversion branches and tags are effectively the same thing – a copy of an existing folder and its contents, in a new location within the same repository. The main difference is the way the user handles branches and tags:

  • Branches – these should be used to work on significant changes, variations of code, and bug fixes.
  • Tags – should be used as “code milestones” that provide a snapshot of your project at a specified point.

In this post, we’ll show you how to create a branch, before providing an example of creating a tag.

Creating a Branch

To create a new branch, use the ‘svn copy’ command followed by a log message (-m) and the URL of both the resource being branched, and the location where you want to create your new branch:

svn copy -m “Creating a new branch” folder-being-branched location-of-new-branch

In this example, we are creating a new branch called ‘bug fix branch’ inside the ‘branches’ folder, that will contain all the files in the trunk:

Creating a Tag

Creating a tag uses exactly the same command, although it is good practice to create a dedicated ‘tags’ folder, where you can store all your tags.

In this example, we are creating a new tag called ‘Release1,’ again by copying the files currently in the trunk.

Tip. Whether you are creating a branch or a tag, it’s worth putting some thought into your naming strategy. A coherent naming strategy allows other team members to get an insight into what development work is happening in which branch/tag, at a glance.

Subversion Tip of the Week

Updating to a Particular Revision From the Command Line

When updating your working copy in Apache Subversion, you usually run the ‘SVN Update’ command and update to the HEAD revision. However, in some instances you may need to update your working copy to a particular revision – or even revert to a previous revision. This is achieved by running the ‘SVN Update’ command and specifying your target revision with the -r command:

svn update -r revision-number

You working copy will now be at the specified revision! In addition, there are several commands that you may find useful when targeting a particular, non-HEAD revision:

1) Find out which revision you’re currently at:

svn log -q -r BASE

2) Find out which revision is the HEAD:

svn log -q -r HEAD

3) See what’s changed between your working copy revision and HEAD:

svn log -r BASE:HEAD

Top 5 Reasons To Try SmartSVN

SmartSVN is WANdisco’s powerful graphical client for Apache Subversion. In this post, we run through our top five reasons to try SmartSVN.

1) It’s Cross Platform

SmartSVN runs on Windows, Linux and Mac OS X, so you can continue to work with your operating system of choice. SmartSVN also offers comprehensive support for all of these operating systems – it integrates with Windows Explorer, and can be started as a background process on Windows and Linux.

SmartSVN integrated with Windows Explorer.

For Apple users, SmartSVN leverages the dock icon to automatically notify users of new transactions, and provides a Finder integration (Mac OS X 10.5).

2) Everything you need, out of the box!

SmartSVN comes complete with all the tools you need to manage your Subversion repositories:

  • Conflict Solver

Conflicts can be tricky for Apache Subversion users, but SmartSVN comes with a dedicated ‘Conflict Solver’ that takes the pain out of resolving them. SmartSVN’s built-in Conflict Solver combines the freedom of a general, three-way-merge with the ability to detect and resolve any conflicts that occur during the development lifecycle.

To access this conflict solver, open the ‘Query’ menu and select ‘Conflict solver.’

In the ‘Mark Resolved’ dialog, you can opt to:

  1. Leave the file/directory as it is.
  2. Accept the version in the working copy, as it was before the update or merge was performed.
  3. Accept the new version – the pristine copy after the update or merge was performed.
  4. Accept the old version – the pristine copy before the update or merge was performed.
  • File Compare

SmartSVN provides file-compare out of the box, combining the ability to compare with inner-line comparisons and the ability to edit the compared files directly.

The ‘File Compare’ option can be easily accessed through the ‘Show Changes’ option in the ‘Query’ menu.

  • Built in SSH Client

SmartSVN’s powerful SSH client allows users to access servers using the SSH protocol. This security-conscious protocol encrypts every piece of communication between the client and the server.

3) See the state of your files/directories at a glance

In the project directory you can see at a glance which directories contain local modifications (red arrows) and which directories have been changed in the repository (green arrows.)

Furthermore, you can easily see whether each file has been modified locally and whether it has been modified in the repository:

4) Optimized Interface

SmartSVN’s interface has been designed to give users an optimal view of their project’s state. This includes:

  • Placing the most ‘important’ files (such as conflicting, modified or missing files) at the top of the file list.
  • See at a glance which directories contain local modifications, which directories have been changed in the repositories, and whether individual files have been modified locally and modified in the repository.
  • Displaying all files – even files that don’t exist locally, or currently only exist in the repository. This is beyond the scope of many Apache Subversion clients.
  • Customize the displayed file information according to your needs.

5) Excellent Merge Support

SmartSVN’s xMerge add-on can take the pain out of merging moved and renamed files. xMerge analyzes the repository’s history and identifies files in the merge source and the merge target using Subversion’s copy-from information. This ensures that files can be located and correctly identified, even after they have been moved and/or renamed. This functionality also preserves a file’s log history with greater accuracy, even when a file has been moved and renamed before being merged.

Find out more about the xMerge add-on http://www.smartsvn.com/xmerge-addon

Ready to get started with SmartSVN? Download your free, 30 day free trial of SmartSVN Professional http://smartsvn.com/evaluate

Results: How Involved are you with Subversion?

One of the major benefits of being part of the Apache Subversion community, is all the opportunities to get involved in the project. Even if you’re not contributing to the actual code base or working on a related client, GUI or Subversion plugin, you can still post useful tutorials, or connect with the community at mailing lists and forums.

We opened a poll a few weeks ago to find out exactly how you’re interacting with Subversion – and the results are in!

As a major corporate contributor to the Subversion project, we’re excited to see the number of people who actively contribute to the project: just over 27% of respondents stated that they either contributed to Apache Subversion, or a related project.

Almost 10% of respondents stated that they read Subversion articles and blogs, while the same amount of respondents post on a Subversion forum. If you’d like to connect with other Subversion users at a dedicated forum, why not take a look at our SVNForum.org?

Thank you to everyone who took part in the poll. We’ll be launching another one shortly, and if you have a question you’d like us to put to the Subversion community, you can either post it here, or Contact Us directly and we’ll try and feature it in future polls.

And, if you’d like to find out more about actively contributing to the Apache Subversion project,  the ASF’s ‘Getting Involved with Apache Subversion’ page is a great place to start.