-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Platform: All, OS: All
Hi,
I moved my jboss (has hudson deployed) to some other linux server. and also
.hudson folder to this linux machine.
when I start the hudson on new server and do a build, my build is not getting
latest svn changes
instead am getting the following message in the console output
WARNING: clock of the subversion server appears to be out of sync. This can
result in inconsistent check out behavior.
WARNING: clock of the subversion server appears to be out of sync. This can
result in inconsistent check out behavior.
any 1 can help to get back my build on track ?
We are also seeing this. We support multiple Hudson servers connecting to
multiple SVN repositories; all the Hudson servers are hosted on Red Hat linux
virtual machines. The Hudson servers are time sync'd with the SVN servers.
One effect is that where projects poll for changes they may occasionally miss an
opportunity to build, so it can be up to twice the polling interval between the
change to SVN and the build starting. When using "build now", we have to wait
for a minute or so before pushing the button.
I would like to understand how Hudson's SVN polling detects changes? Is the
problem likely to be in Hudson's polling code, or the underlying SVN access
library? Why are the dates on the servers even relevant? Can Hudson not detect
changes based on revision numbers alone?