Repository navigation
[JENKINS-1244] Hudson does not check out latest version (endlessly updates + builds) #428
Description
Hi, since a while I have noticed a very strange behavior in Hudson. After a
commit to subversion it starts building the project, and after completion it
starts to build it again and again ad infinitum. This happens in 1.156 and also
in 1.177
The subversion polling always reports that changes are found, but there are no
changes:
Started on 01.02.2008 09:52:40
Revision:27534
Revision:28031
(changed from 27992)
Done. Took 0 seconds
Changes found
The build then starts with this message (servername replaced with xxxxx):
started
Updating https://xxxxxxxx.xxx/koagent/trunk
Fetching external item into 'D:\hudson\jobs\KoAgent
Style\workspace\trunk\lib\required\ensure4j'
External at revision -1
At revision 28031
Fetching external item into 'D:\hudson\jobs\KoAgent
Style\workspace\trunk\src\ensure4j'
External at revision -1
At revision 28031
At revision 28011
no change for https://xxxxxxxx.xxx/koagent/trunk since the previous build
no change for https://xxxxxxxx.xxx/lib/ensure4j/trunk/lib/required since the
previous build
no change for https://xxxxxxxx.xxx/lib/ensure4j/trunk/src/java since the
previous build
[trunk] $ cmd.exe /C '"ant.bat clean test.style && exit %%ERRORLEVEL%%"'
Buildfile: build.xml
...
The workspace shows that hudson is checking out an old version of
https://xxxxxxxx.xxx/koagent/trunk, it does not use the latest version! This
happens with both "Use update" and without the option (There the workspace is
correctly deleted, and the freshly checked out version is still not the last
version in subversion).
Originally reported by martinankerl, imported from: Hudson does not check out latest version (endlessly updates + builds)
- status: Closed
- priority: Major
- component(s): subversion-plugin
- resolution: Fixed
- resolved: 2008-02-03T18:16:28+00:00
- votes: 0
- watchers: 0
- imported: 20251212-090250
Raw content of original issue
Hi, since a while I have noticed a very strange behavior in Hudson. After a commit to subversion it starts building the project, and after completion it starts to build it again and again ad infinitum. This happens in 1.156 and also in 1.177
The subversion polling always reports that changes are found, but there are no changes:
Started on 01.02.2008 09:52:40 Revision:27534 Revision:28031 (changed from 27992) Done. Took 0 seconds Changes found
The build then starts with this message (servername replaced with xxxxx):
started Updating https://xxxxxxxx.xxx/koagent/trunk Fetching external item into 'D:\hudson\jobs\KoAgent Style\workspace\trunk\lib\required\ensure4j' External at revision -1 At revision 28031 Fetching external item into 'D:\hudson\jobs\KoAgent Style\workspace\trunk\src\ensure4j' External at revision -1 At revision 28031 At revision 28011 no change for https://xxxxxxxx.xxx/koagent/trunk since the previous build no change for https://xxxxxxxx.xxx/lib/ensure4j/trunk/lib/required since the previous build no change for https://xxxxxxxx.xxx/lib/ensure4j/trunk/src/java since the previous build [trunk] $ cmd.exe /C '"ant.bat clean test.style && exit %%ERRORLEVEL%%"' Buildfile: build.xml ...
The workspace shows that hudson is checking out an old version of https://xxxxxxxx.xxx/koagent/trunk, it does not use the latest version! This happens with both "Use update" and without the option (There the workspace is correctly deleted, and the freshly checked out version is still not the last version in subversion).
- environment:
Platform: All, OS: All
Activity
jenkins-infra-bot commentedon Feb 1, 2008
martinankerl:
Raw content of original comment:
I have just noticed that for other projects the build does not start at all,
subversion does not seem to detect the changes:
Started on 01.02.2008 11:51:41
Done. Took 0 seconds
No changes
No changes detected, but there have been at least 10 commits since the last
build. I am polling every 5 minutes, and the commits happened a day ago. The
previous build (a day ago) failed because some files could not be removed from
the workspace.
jenkins-infra-bot commentedon Feb 1, 2008
martinankerl:
Raw content of original comment:
I have finally found the source of the problem: our subversion server was
configured with the wrong time, it was about two hours in the future. Hudson
seems to use time stamps in class CheckOutTask from SubversionSCM.java, so it
always check out a release that was checked in two hours ago.
So this is not really a bug in hudson, but it is very important both the
subversion server and hudson are configured with the correct time. I am not sure
what happens if hudson and the subversion server are in a different time zone.
jenkins-infra-bot commentedon Feb 3, 2008
Raw content of original comment:
Yes, this is one of the very common problems.
In 1.180, I modified Hudson so that it tries to detect this problem (in the
obvious situation where the latest revision in SVN is dated later than the
current timestamp on Hudson.)
jenkins-infra-bot commentedon Feb 4, 2008
Raw content of original comment:
jenkins-infra-bot commentedon Dec 12, 2025
[Original
is_duplicated_byfrom Jira: JENKINS-1043]