Tag Archive for 'poll'

Page 2 of 2

Bringing Order to Your Jenkins Jobs

Once you’ve been working with Jenkins and uberSVN for a while, you may find yourself in a situation where you have several jobs that need to run in a specific order, for example:

  • Job 1 and Job 3 can run simultaneously.
  • BUT Job 2 should only start when Job 1 and Job 3 have finished running.
  • AND Job 4 should only start when Job 2 has finished.

How can you implement this complicated setup? This is where Jenkins’ ‘Advanced Project Options’ and build triggers come in handy. In this tutorial, we’ll walk through the different options for scheduling jobs using Jenkins and uberSVN, the free ALM platform for Apache Subversion.

Note, this tutorial assumes you have already created a job and configured it to automatically poll your Subversion repository.

1) Open the Jenkins tab of your uberSVN installation and select a job.

2) Click the ‘Configure’ option from the left-hand menu.

3) In the ‘Advanced Project Options’ tab, select the ‘Advanced…’ button

4) This contains two options that are useful for ordering your jobs:

  • Block build when upstream project is building – blocks builds when a dependency is in the queue, or building. Note, these dependencies include both direct and transitive dependencies.
  • Block build when downstream project is building – blocks builds when a child of the project is in the queue, or building. This applies to both direct and transitive children.

If this option doesn’t meet your needs, you can explicitly name a project (or projects) that must be built before your job is allowed to run. To set this:

1) Scroll down to the ‘Build triggers’ tab on the configure page.

2) Select the ‘Build after other projects are built’ checkbox. This will bring up a text box where you can list any number of projects.

Utilized properly, the build triggers and advanced project options should allow you to organize your jobs into a schedule. Tip, if you need even more control over your build schedule, there are plenty of scheduling plugins available. To add plugins to Jenkins, simply:

1) Open the ‘Manage Jenkins’ screen.

2) Click the ‘Manage Plugins’ link.

3) Open the ‘Available’ tab and select the appropriate plugins from the list.

Not yet using uberSVN? It’s free to download, free to use, and is seamlessly integrated with Jenkins. Simply visit http://www.ubersvn.com/ to get started. A professional support option for Jenkins is also available.

Poll Results: Which Subversion Client Do You Use?

There’s no shortage of clients for Apache Subversion, each with its own combination of functionality, integration capabilities, and target platforms. But which client is the most popular with the SVN community? We recently ran a poll to find out and, after getting a great response, the results are in and there’s a clear winner…

Over 60% of respondents said they used TortoiseSVN, an SVN client for the Windows operating system.

It’s easy to see why TortoiseSVN is so popular with the community: not only does its context-sensitive menu integrate seamlessly with Windows shell, but it allows users to see the status of their files at a glance, thanks to its handy icon overlays. And, of course, just like Subversion it’s an established open source project with the option of professional support, for those who need some extra help with their implementation.

The poll also revealed the popularity of Subversion clients in general, with less than 5% of respondents saying they do not use a client.

Thank you to everyone who took part in our poll and if there’s a question you’d like to pose to the Subversion community, don’t hesitate to contact us with your ideas and we’ll try to feature them in future polls.

If you want to find out more about what TortoiseSVN has to offer, why not take a look at our ‘Top Ten Reasons To Try TortoiseSVN’ blog post? If you want to find out what all the fuss is about for yourself, we also have a handy starter guide: ‘How to Install TortoiseSVN and Make Your First Repository Change.’

Poll: Which Subversion Client Do You Use?

Like any successful open source project, Apache Subversion is at the centre of a vibrant ecosystem of client tools, GUIs and plugins. There’s no shortage of clients for Subversion, but each has different functionality and integration capabilities, and some target specific platforms. We want to find out which client is best-suited to the needs of the SVN community. Let us know, by taking our quick poll.

We’ll publish our results in a couple of weeks, so you can see which clients are popular with other Apache Subversion users.

Want to move beyond the client? We have some free introductory tutorials to get you started with command line Subversion: Intro to Command Line Subversion and Working with Files from the Subversion Command Line.

Advanced Subversion Polling with Jenkins: File Fingerprints

In ‘Polling Subversion with Jenkins’ we showed you how to configure Jenkins to poll an Apache Subversion repository once every five minutes. In this follow-up post, we’ll explore some advanced options you can introduce once you’ve implemented the basic polling system. This post will show you how to configure Jenkins to automatically track versioned files using ‘file fingerprinting.’

In the world of modern software development, it’s common practice to work on different projects simultaneously. 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, and even to upload a file from your local machine and query Jenkins on its version number. File fingerprinting works by creating a database of MD5 checksums, which gets updated automatically as new versions of fingerprinted files are committed to the repository.

How To: Setup File Fingerprinting

1. To enable file fingerprinting in uberSVN, simply select the ‘Jenkins’ tab, followed by the Jenkins job you previously setup to poll Subversion.

2. Select the ‘Configure’ option from the left-hand menu.

3. Tick the ‘Record fingerprints of files to track usage’ option.

4. Specify the files to track in the ‘Files to fingerprint’ text box. In this example, trunk/*.txt will track all .txt files in the trunk (if you wanted to track all .zip files in the tags directory, you would use tags/*.zip)

How To: Test Your File Fingerprinting

1. To test your setup, make some changes to the files earmarked for fingerprinting, and commit those changes.

2. Open the build report in Jenkins, and select ‘See Fingerprints’ to view the recorded fingerprints.

3. This screen will display some basic details about the tracked files, including the original owner, and how old the information is. To see more, click on the ‘more details’ link.

4. On this page, you can see all the jobs and builds where the file has been used.

How To: Check File Fingerprint

Another benefit of enabling file fingerprinting, is that if you have a file on your local machine but are unsure of its version number, you can upload it to Jenkins and check the fingerprint against Jenkins’ fingerprint database.

1. Start by selecting the ‘Check File Fingerprint’ option from the main Jenkins dashboard.

2. Upload your file and select ‘Check’ to run it against Jenkins’ database of file fingerprints.

3. Jenkins will then display all the information about the uploaded file.

Not yet started with uberSVN? It’s free to download and free to use! You can download the latest version now from http://www.ubersvn.com/ If you need some extra support with your Jenkins+uberSVN installation, Professional Support for Jenkins is also available.

Give us your Feedback on the uberAPPS Store

Tell us what you think

It’s been a busy few months for uberAPPS, the integrated app store for uberSVN, not only have we added professional support for Jenkins and uTest’s crowdsourcing services, but professional support for TortoiseSVN and uberSVN Support Starter Packs are now also available through uberAPPS.

We hope you are enjoying using uberSVN and uberAPPS! We’ve had some great feedback so far, but now we need your help to make the uberAPPS experience even better. Is there a particular app that would be a perfect fit for your uberSVN installation? Or an ALM component that would make your life easier? We’ve created a quick and easy online poll for our users, so we can continue to bring the uberSVN community the functionality they need.

As always, if you have any comments or questions about uberSVN, please do not hesitate to contact us directly. We look forward to hearing your feedback.

Poll Results: Are You using Subversion 1.7 Yet?

At WANdisco, we’re convinced that Apache Subversion 1.7 is a great release. Not only did it completely overhaul the working copy metadata system, but it added support for HTTPv2 and a new remote dumpfile tool. But, we wanted to know how many of you had already made the switch to Apache Subversion 1.7 – so earlier this month, we held a poll at SVNForum.org, to find out who has switched, who is planning to, and who is content to stick with their earlier release of Subversion.

Click on the thumbnail below to see the full results of our poll:

Thank you to everyone who took part in our poll! We had a great response from the Subversion community.

Do you have a burning, SVN-related question you would like to put to the Subversion community? We’ll be running regular polls throughout the year, so feel free to post your poll ideas in the Comments section or, alternatively, contact us directly.