Tag Archive for 'uberSVN'

Page 2 of 10

WANdisco’s August Roundup

This month we announced some exciting releases for the Apache Subversion community: the release of Subversion 1.7.6, and updates for uberSVN and TortoiseSVN.

Building on the 1.7 series, Apache Subversion 1.7.6 added even more fixes and enhancements for the SVN community:

  •  A fix for running tests against httpd version 2.4
  • Constant struct initialisers now used for C89 compatibility
  • Fixes for the output of ‘svn propget -R’ ‘svn proplist’ and ‘svn status’
  • Optimized ‘svn upgrade’ performance on large working copies
  • A fix for ‘svn upgrade’ on working copies with certain tree conflicts
  • Fixes for two asserts into errors for TortoiseSVN

More information on what’s new in Subversion 1.7.6 can be found in the Changes file. As always, if you want to get your hands on the latest, certified binaries you can do so from our website. The latest version of TortoiseSVN – 1.7.8 – is also available for download. This release is linked against Subversion 1.7.6, and features a list of bug fixes. For more information on all the updates and fixes in TortoiseSVN 1.7.8, check out the Changelog.

The uberSVN community also saw an update, as the WANdisco developers finished off uberSVN ‘Chimney House’ Release 3.

uberSVN ‘Chimney House’ Release 3 features many improvements and enhanced functionality for uberSVN’s ever-growing community of users. These include:

  •  Further improvements to the way uberSVN handles LDAP and LDAPS.
  • Improvements to uberSVN APIs and internal development of the uberSVN SDK (public release coming soon!)
  • New manageAPPS page allows you to see metadata attached to your APP license, such as expiry date, number of named users, and more.
  • A list of bug fixes, including some fixes and alignment/mapping of the uberSVN Access Control Team Leader and uberSVN Delegated Team Admin (where uberSVN Access Control is active)
We also conducted a community poll to find out more about how you’re using Subversion. We asked what operating system your Subversion server is running on and, once again, there was a very clear winner…..

You may have already noticed that we’ve been adding new Subversion refcards. We’ve had such a great response that we’ve already put together two more – ‘All About the Apache Subversion Commit Command’ and ‘All About Checkouts.’ The first covers everything from the basic “what is a commit?” to more advanced information on editing log messages, ignoring files and directories, and an intro to hook scripts. ‘All About Checkouts’ provides a quick reference to making full use of the checkout command and understanding the messages generated under different scenarios.

We hope you’re enjoying these latest refcards, and if have any ideas for future refcards, please do not hesitate to Contact Us. If you’re after more Apache Subversion know-how, then why not take a look at our upcoming Subversion Live conference?

On the enterprise side of things, we published a new case study of our enterprise-class Subversion MultiSite product. The case study looks at how global logistics technology leader Navis – a subsidiary of Cargotec, enjoyed a 10x improvement in Subversion performance and achieved 24-by-7 uptime across all of their development sites after implementing our Subversion MultiSite solution. Read the Navis case study in full to find out more.

Also this month, WANdisco CEO and co-founder David Richards was asked to do an interview with BloombergTV – check out the full video interview below!

Finally our friend, photographer Matt Lollar popped into the office to take some new snaps of WANdisco’s Sheffield office.

 

Creating Your First Job in Jenkins with uberSVN

As uberSVN fans will already know, Jenkins has been available as a free, easy-to-install download through uberSVN since April 2011, and we have since extended our partnership with CloudBees to offer professional support for Jenkins.

uberSVN makes the popular Jenkins continuous integration server easy-to-install and easy-to-download, bringing benefits such as the automatic creation of software builds to Apache Subversion users. Getting started with Jenkins in uberSVN couldn’t be easier. Once you have Jenkins installed in uberSVN, your first task is to create a Jenkins job, and in this short tutorial, we’ll cover exactly this.

1) From uberSVN’s ‘repositories’ tab, select the repository you wish Jenkins to be associated with. In this example, we will use the ‘New Project’ repository.

2) Select the secondary ‘Jenkins’ tab. In the subsequent ‘Job Creation’ screen, enter a name for your job and a description, and click ‘Create.’

3) You will then be prompted to configure your job, by selecting available options for how you want your job to be set up (email notifications, publish JUnit test result reports, source code management, etc.) When you are happy with the configuration, click ‘Save.’

4) When you view your repository in uberSVN you will notice that a new ‘Jenkins’ tab has been added, which contains the job you have just created.

5) To start the job, click on the ‘New Jenkins Job’ link. On the subsequent page, select ‘Build Now’ to start Jenkins.

You have now successfully created your first Jenkins job in uberSVN.

Need more Subversion know-how? After getting a great response from the Apache Subversion community in 2011, Subversion Live is back for 2012, bringing the Subversion community sessions covering everything from Subversion’s future, to expert-led best practices workshops, as well as the unique opportunity to meet the core Subversion committers..

Subversion Tip of the Week

Quickstart: Getting Started with Jenkins and Subversion

The Jenkins open source continuous integration server can be a valuable tool for Apache Subversion users. It can be configured to watch for code changes in repositories, to automatically perform builds, to notify users, and perform other useful tasks on both remote and local machines. The easiest way to integrate Jenkins with Subversion, is through uberSVN and its integrated uberAPPS store. In this easy, five step guide, we’ll walk you through installing Jenkins in uberSVN.

1) Select the ‘uberAPPS’ tab from within ‘uberSVN’ to be taken to the store front, where you can select Jenkins.
2) From the Jenkins product screen, click ‘Download Now’ to download Jenkins.

3) Once the download is complete, click ‘Activate.’
4) You will notice a new Jenkins tab appear. Select this tab to go to uberSVN’s integrated Jenkins screen.

5) From here, you can optionally decide whether to make Jenkins visible to all users, or define exactly who can access the tool.

Get started with uberSVN now – download it for free from http://www.ubersvn.com/

Need more Subversion know-how? After getting a great response from the Apache Subversion community in 2011, Subversion Live is back for 2012, bringing the Subversion community sessions covering everything from Subversion’s future, to expert-led best practices workshops, as well as the unique opportunity to meet the core Subversion committers.

Switching to Apache Subversion 1.7.6

Keeping up-to-date with software updates can be a time-consuming chore, but upgrading to new releases of Apache Subversion needn’t be stressful. uberSVN, the free, open ALM platform for Subversion users comes with an innovative ‘SVN Switch’ feature that allows administrators to upgrade SVN binaries with a simple mouse click and a service restart.

In this post, we’ll show you how to upgrade to Apache Subversion 1.7.6 in uberSVN, in five easy steps.

1) In your uberSVN installation, open the ‘Administration’ tab followed by the ‘SVN Switch’ tab.

2) On the ‘SVN Switch’ screen, select the ‘Subversion 1.7.6’ option.

3) Click ‘Apply.’

4) uberSVN will begin the process of changing the Subversion binaries. Note, this may take a few minutes to complete.

5) Once the binaries have been changed, uberSVN will automatically log you out. Re-enter your login details.

You’ve now successfully upgraded to Apache Subversion 1.7.6!

Need more Subversion know-how? After getting a great response from the Apache Subversion community in 2011, Subversion Live is back for 2012, bringing the Subversion community sessions covering everything from Subversion’s future, to expert-led best practices workshops, as well as the unique opportunity to meet the core Subversion committers.

Configuring Jenkins: Security

The Jenkins continuous integration system doesn’t perform any security checks by default. While this may not be a problem in certain situations, if your installation is going to be exposed to the internet (or any other untrusted environment) it’s a good idea to implement some security checks. In this example, we’ll walk you through a common setup: allowing Jenkins to maintain its own user database, and then show you how to grant a specified user with full administrative privileges.

Note, this tutorial uses Jenkins and uberSVN. uberSVN is free to download and free to use, simply visit http://www.wandisco.com/ubersvn to get started.

1) Open the ‘Jenkins’ tab in your uberSVN installation and select the ‘Manage Jenkins’ option.

2) Select the ‘Configure Systems’ option.

3) Select the ‘Enable security’ option. This will bring up some additional options.

4) Select ‘Jenkins’s own user database’ under the ‘Security Realm’ heading, and ensure the ‘Allow users to sign up’ checkbox is ticked.

5) Under ‘Authorization,’ select ‘Matrix-based security.’ This will bring up a new table.

6) In the table select ‘Overall – Read’ for anonymous users.

7) Type your username into the ‘User/group to add” box and click ‘add.’ Your username will now appear in the table.

8) Make sure every permission for your username is ticked, to give yourself full access.

9) Select the ‘Save’ button at the bottom of the page. You have now configured Jenkins’ security settings!

Need more Subversion know-how? After getting a great response from the Apache Subversion community in 2011, Subversion Live is back for 2012, bringing the Subversion community sessions covering everything from Subversion’s future, to expert-led best practices workshops, as well as the unique opportunity to meet the core Subversion committers.

Apache Subversion 1.7.6 Arrives

Apache Subversion 1.7.6 has been released, bringing even more fixes and enhancements to the world’s most popular open source version control system.

Here is just some of what’s new and noteworthy in the 1.7.6 release:

  • A fix for running tests against httpd version 2.4
  • Constant struct initialisers now used for C89 compatibility
  • Fixes for the output of ‘svn propget -R’ ‘svn proplist’ and ‘svn status’
  • Optimized ‘svn upgrade’ performance on large working copies
  • A fix for ‘svn upgrade’ on working copies with certain tree conflicts
  • Fixes for two asserts into errors for TortoiseSVN

More information on what’s new in Subversion 1.7.6 can be found in the Changes file.

As always, the latest, certified binaries can be downloaded for free from the WANdisco website, and are also available through the award winning, open uberSVN platform. Upgrading to Subversion 1.7.6 is made easy with uberSVN, which features an innovative svnSWITCH tool for moving between the different binaries.

If you want all the latest news, tips, tricks and best practices on Apache Subversion, then why not check out Subversion Live 2012, the series of dedicated Subversion conferences? This year, events will be taking place in London, San Francisco and Greenwich, Connecticut, and will feature a unique mix of sessions, expert-led best practices workshops and invaluable networking opportunities for the SVN community.

Jenkins: Configuring a Proxy

In most setups, the Jenkins server is behind a firewall, which can be a problem as Jenkins requires internet access to download plugins and updates. If you need to go through an HTTP proxy server, the connection details can easily be configured in Jenkins’ ‘Manage Plugins’ tab.

Note, this tutorial uses uberSVN. If you don’t already have uberSVN, you can download it for free from http://ubersvn.com/

1) Open the ‘Jenkins’ tab of your uberSVN installation.

2) Select the ‘Manage Jenkins’ link.

3) Click the ‘Manage Plugins’ link.

4) In the ‘Plugin Manager’ open the ‘Advanced’ tab. This will bring up your HTTP Proxy information. Enter the appropriate info – such as port, server, etc. – and click ‘Submit.’

Jenkins will now have internet access, and will be able to download updates and plugins.

Updating Jenkins

To download Jenkins plugins, simply click the ‘Available’ tab of the ‘Plugin Manager’ to see a list of available plugins.

Updates for your installed plugins can be found in the adjoining ‘Updates’ tab.

Once you’ve configured internet access, you’ll have access to updates for Jenkins itself. To check for Jenkins updates:

1) Open the ‘Administration’ tab, followed by the ‘Updates’ tab.

2) Click the ‘Check for Updates’ tab to ensure you have all the latest updates.

3) You will then be able to see – and install – all the latest Jenkins updates.

Not yet started with uberSVN? It’s free to download, free to use and integrates seamlessly with Jenkins. Simply visit http://www.ubersvn.com/ to find out more.

Need more Subversion know-how? After getting a great response from the Apache Subversion community in 2011, Subversion Live is back for 2012, bringing the Subversion community sessions covering everything from Subversion’s future, to expert-led best practices workshops, as well as the unique opportunity to meet the core Subversion committers.

New Refcards: All About Subversion Checkouts and Commits

Need an intro to some essential Apache Subversion commands? We got such great feedback from last month’s branching and merging refcards, that we’ve already put together two more free refcards for the Subversion community.

All About the Apache Subversion Commit Command’ covers everything from the basic “what is a commit?” to more advanced information on editing log messages, ignoring files and directories, and an intro to hook scripts.

Meanwhile, ‘All About Checkouts’ provides a quick reference to making full use of the checkout command and understanding the messages generated under different scenarios. This refcard covers:

  • What is a checkout?
  • Performing a checkout from the command line
  • Performing a checkout with TortoiseSVN
  • How to create a nested folder
  • Changing the checkout file data

We’ve got even more refcards lined up for the coming weeks, so be sure to keep checking back for all the latest free training content. And if you’ve got an idea for a Subversion refcard, please don’t hesitate to Contact Us.

Need more Subversion know-how? After getting a great response from the Apache Subversion community in 2011, Subversion Live is back for 2012, bringing the Subversion community sessions covering everything from Subversion’s future, to expert-led best practices workshops, as well as the unique opportunity to meet the core Subversion committers.

uberSVN Update for ‘Chimney House’ Users

We’re pleased to announce an update to uberSVN ‘Chimney House’ that includes a new and improved manageAPPS page and LDAP enhancements.

uberSVN ‘Chimney House’ 3 features plenty of improvements, including:

  • Improvements to uberSVN APIs and internal development of uberSVN SDK (public release coming soon!)
  • New manageAPPS page allows you to see metadata attached to your APP license, such as expiry date, number of named users, and more.
  • Further improvements to the way uberSVN handles LDAP and LDAPS.
  • The latest Apache Subversion 1.7.5 binaries set to active by default.
  • A list of bug fixes, including some fixes and alignment of the uberSVN Access Control Team Leader and uberSVN Delegated Team Admin (where uberSVN Access Control is active)

You may have already heard, but with the latest release of Chimney House, we’re splitting uberSVN’s release cycle into two distinct phases. At least a few weeks before an update is released to the entire uberSVN user base, we’ll be giving our Latest Release Channel users a sneak preview of upcoming features and functionality. These users will get to test new features and see how they fit into the ALM environment before the update becomes widely available. Interested? Check out our blog post announcing the Latest Release Channel for more info.

For the full list of bug fixes, new features and improvements in uberSVN ‘Chimney House’ Release 3, see our Release Notes.

Not yet using uberSVN? It can be downloaded for free from http://www.ubersvn.com/

avatar

About rbudas

Rob Budas has over 25 years of software industry experience, with the last 15 years focused on the Software Configuration Management sector. Prior to joining WANdisco, Rob had worked at IBM Rational for 8 years where he was a Sr. Product Manager for Rational ClearCase. He has held various development, technical sales and product management roles throughout his career. Rob holds a Bachelor of Science in Computer and Communication Science from the University of Michigan.

Subversion Tip of the Week

Apache Subversion: Basic Workcycle

In Apache Subversion, the basic workcycle follows the ‘checkout-edit-update-commit’ format.

A ‘Checkout’ is the process of pulling all the files from your repository onto your local machine, where it becomes known as a ‘working copy.’ You can then work on these files in isolation, before sharing your work with the rest of the team by ‘committing’ back to the repository.

In this week’s tip, we’ll provide a handy introduction to this basic workcycle.

Checkout

To checkout a working copy, run the ‘svn checkout’ command, followed by the URL of your repository and the location where you wish to create the working copy.

In this example, we’re creating a working copy on the desktop, in a file called ‘Repo’:

Tip, if you’re using the free uberSVN platform, you can easily find out your repository’s URL by opening the ‘Repositories’ tab.

You can now edit the files and folders in your working copy.

Update

You may be ready to share your changes with the rest of your team, but it’s good practice to perform an SVN update first. This will pull any changes your colleagues may have already committed, into your working copy, ensuring your changes fit with the most up-to-date version of the project.

To perform an update, run the ‘svn update’ command, followed by the location of your working copy.

svn update (working copy location)

Commit

Let’s assume any changes your team committed are compatible with your changes, and go ahead with the commit. When performing a commit, you should leave a log message and include as much information as possible, as this can be an invaluable source of information if you ever need to revisit this revision. When performing a commit, the log message is entered in the “–m” format (for example, -m “added ReadMe file.”)

The commit itself is performed using the ‘svn commit’ command, followed the log message and the location of the working copy.

svn commit -m “log message” (working copy location)

In this example, we are performing a commit with the log message “added Admin Guide text.”

Need more Subversion know-how? After getting a great response from the Apache Subversion community in 2011, Subversion Live is back for 2012, bringing the Subversion community sessions covering everything from Subversion’s future, to expert-led best practices workshops, as well as the unique opportunity to meet the core Subversion committers. We’re currently running a very special early bird offer: register now using the ‘earlybird’ code to get a 25% discount (note, the early bird offer ends 10th August, so you better be quick!)