Polling Subversion with Jenkins: More Options

Not only does uberSVN, the open ALM platform, make Apache Subversion easy, but users can leverage the functionality of other tools without even leaving their uberSVN installation. We’ve already looked at configuring Jenkins to poll an Apache Subversion repository, and using Jenkins’ file fingerprinting functionality. In this post, we’ll show how Jenkins’ polling functionality can be further configured to perform the following tasks:

  • Automatically sending out email notifications about broken builds.
  • Archiving specified artifacts whenever a new build is created.

Email Notifications

Jenkins can be configured to send email notifications whenever a build becomes unstable, fails, or returns to stable. uberSVN makes this configuration easy:

1. To get started, select the ‘Jenkins’ tab followed by the Jenkins job you previously setup to poll Subversion.

2. Select the ‘Configure’ option from the Jenkins side-menu.

3. Select the ‘E-mail Notification’ checkbox, enter the appropriate email addresses and click ‘Save.’

And that’s it! Now, whenever there are problems with your builds, Jenkins will automatically send out email notifications, allowing you to identify problems early.

Archive Artifacts

Jenkins can also be setup to archive certain ‘artifacts’ (i.e any results of your build process) whenever a new build is created. The advantages of archiving artifacts is that they’re easily accessible via uberSVN’s interface, and you only have to setup backup on your master.

1. Repeat steps 1 and 2 to open the ‘Configure’ screen of the Jenkins job that will be in charge of archiving.

2. Select the ‘Archive the artifacts’ option.

3. Now it’s time to specify which artifacts to archive. If you just want to archive one file, enter that artifact’s name and location. For example, to archive the Project Wiki text file in the trunk directory, enter:

trunk/Project Wiki.txt

Alternatively, you can configure Jenkins to archive every file of a particular format. If you wanted to archive every text document in the trunk directory, you would enter:


Or, if you wanted to archive every .zip file in the tags directory, the command is:


4. At this point, you can optionally instruct Jenkins to overwrite previous artifacts by selecting the ‘Discard all but the last successful/stable artifact to save disk space’ option, which is accessible through the ‘Advanced’ menu.

5. Once you are happy with the changes you have made, click ‘Save.’

6. To see archiving in action, make some changes to the files you’ve configured Jenkins to archive and commit them back to the repository.

7. Once Jenkins has polled Subversion and created a new build, you will see new artifacts at the job’s status page.

8. Click on an archived item, to see its contents.

Need some extra support with your Jenkins+uberSVN installation? We offer Professional Support for Jenkins that provides:

  • 24-by-7 online, phone and email support.
  • Guaranteed response times.
  • Automated delivery of fixes and upgrades.
  • …and more!

0 Responses to “Polling Subversion with Jenkins: More Options”

  • No Comments

Leave a Reply