|
| Re: hudson and .svn [message #903733 is a reply to message #903731] |
Sat, 25 August 2012 08:11   |
|
The svn update you are doing manually is being done on an older version of svn, probably 1.6. Hudson uses svn 1.7 by default which is said to have some major speed improvements.
The tree structure for svn 1.6 is to put a .svn folder in each individual folder, where svn 1.7 puts the .svn folder in the root location which is why you are seeing less.
To validate my theory, run "svn --version" via command line and make sure to update to the latest version, either that or go into manage hudson > configure system and change the workspace version to 1.6(svn:external to file).
/**
* @author Steven Christou
* @dev Hudson-ci
*/
|
|
|
| Re: hudson and .svn [message #903734 is a reply to message #903733] |
Sat, 25 August 2012 08:25 |
 Maxim Kiselev
Messages: 11
Registered: August 2012 |
Junior Member |
|
|
I don't know why, but I can't set in hudson > configure system svn 1.7 at all(hudson version 2.2.1) and there is set 1.6(svn:external to file).
"svn --version" in hudson build step returns: svn, version 1.6.17 (r1128011)
My client has 1.6.17 too and because differents in .svn structures are puzzle for me...
[Updated on: Sat, 25 August 2012 08:27] Report message to a moderator |
|
|
| Re: hudson and .svn [message #903736 is a reply to message #903734] |
Sat, 25 August 2012 09:38 |
|
What version of the svn plugin are you using? I believe you are using an older version. I accidentally released a version with svn 1.7, but forgot to put that as an option. Make sure version 2.3.3 is installed.
When you do svn --version though a build step you will see the same version because the svn plugin has it's own svn library called svnkit (version 1.7.4) which allows you to do things like svn update without having to actually install svn.
/**
* @author Steven Christou
* @dev Hudson-ci
*/
|
|
|
|
|
| Re: hudson and .svn [message #903741 is a reply to message #903740] |
Sat, 25 August 2012 10:59 |
|
Yes you are right! After upgrading the pom.xml file to 2.2.1 I am finding that a couple critical test units are failing. The pom is currently set for 2.2.0 which seems to have no issues. I will fix these and run a quick test along with a release for it ASAP.
/**
* @author Steven Christou
* @dev Hudson-ci
*/
|
|
|
Powered by
FUDForum. Page generated in 0.03506 seconds
] 
Search
Help
Register
Login
Home
