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 HOUR DOM MONTH DOW
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.