Menu
I use the Jenkins Subversion plugin to checkout a working copy in Jenkins. A separate SVN client is used to extract some information from this working copy (which branch was used, which revision, etc.).
The Subversion plugin creates a 1.7 working copy, which the other client can't handle (it is 1.6). Is there a way to configure the Subversion plugin to checkout a 1.6 working copy?
This question lists a way to configure the Subversion plugin: Hudson doesn't checkout using symlinks when using SVN (Subversion) So I started looking for all configuration options, and ended up on this page: http://svnkit.com/kb/user-guide-config-settings.html , but it is really incomplete.
Also I found this: http://wiki.svnkit.com/SVNKit_FAQ#Q:_Can_the_current_SVNKit_version_be_forced_to_create_pre-1.5_format_working_copies.3F , except that that property is ignored for new directories.
I cannot use Jenkins variables to extract the branch and revision information, because the same script must also be able to run outside Jenkins. Updating the separate client is also not possible, because we are working with 'frozen' software on build systems. If all else fails I could downgrade Jenkins, but that's not preferred.
897
Now create a Jenkins build job. Select New Item, give the build project a name such as svn-tomcat-demo, select Maven project, and click OK. Under source code management, select Subversion and enter your SVN repository URL and credential. Please download the sample code and check the code into your SVN server.
Next to the Repository URL text box click the question mark. In that box will be the following text: "click this link and specify different credential". Click on that link to open the Subversion Authentication page. On that page enter the root of the repository URL, enter the login and password to use and click OK.
Jenkins can poll Subversion repositories for changes, and while this is reasonably efficient, this can only happen up to every once a minute, so you may still have to wait a full minute before Jenkins detects a change.
Essentially, what you can do is setup a svn commit hook that sends a signal to Jenkins to kick off a build. Jenkins will then (given the right build setup) pull the freshly-committed code and run the build. Jenkins is very capable, but it's not intended to be the Ultimate Build System all by itself.
On main Jenkins configurations page (http:/<jenkins_server>/configure) search for Subversion Workspace Version and set it to appropriate value (1.6).
60
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
