Hudson Checking out "sticky revision" - any suggestions?

Posted Wed, 23/09/2009 - 20:02 by hagzag
, , , ,

I am facing a simple Hudson Master-Slave configuration task which must of worked in half a dozen installation's of Hudson, where master server machine is Linux and Slave Machine is Windows 2003.

Agent initializes seamlessly as a windows service (one of the cool features of Hudson by the way - since release 1.321).

 

I configure a simple "free-style" project which has an svn location it is supposed to checkout from http://... /svn/repos/trunk

The issue is if I checkout the same url and run svn info I get revision # 45943 although when Hudson checked out the project it states "Checked out revision 45902"

I am running on 1.321 version of Hudson, I have reconfigured the Job, cleaned up the workspace on the remote slave and the Master machine - and it still seems to poll an old revision from svn and idea why this could happen?

 

Thanks Guys,

‹ A license distribution product automated deployment with maven ›

Comments

by lior.kanfi - 24/09/2009 - 08:38

I would try to get more info using the following methods:
1. try to us the notation http://.../trunk@45943 and see if you get the right revision
2. also try to print the environment variable SVN_REVISION as see it match the "checked out revision"
3. last, try to print out the WC revision using this tool http://www.manpagez.com/man/1/svnversion/

All suggestion are part of Hudson help.

by hagzag - 24/09/2009 - 18:37

I tried all the above,

I checked out the same svn url from SVN to a "standard" working copy, and ran svnrevision / svn info and I found the build is indeed in the revision I am expecting.

I also added to hudsons builder echo %SVN_REVISION% - which also resulted in the wrong revision!


Apparently the Slave Build Server and the SVN server time weren't in sync
The way I found this was by asking the client to perform the same build again but instead of running it on the slave host run it on the master. This was the notice Hudson Master knew to give (and slave didn't):

"WARNING: clock of the subversion server appears to be out of sync. This can result in inconsistent check out behavior."


Once I synced the clocks on both servers - Build is checking out as desired.