You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[JENKINS-1282] since build 180 hudson is "stuck" after checking out from SVN #431
Builds 180, 181, 182, 183 have teh same behaviour for me. Hudson checks out
everything from svn and then just waits. In that situation after clicking the
Red X button (that is supposed to cancel the build) the Hudson build gets
unstuck and continues (without canceling the build).
I had rolled back to 179 and build no longer gets stuck after the svn checkout.
I'm guessing it somehow related to 1244 as I have problems before with "no
changes" builds.
Environments is Solaris 10, Hudson runnning as a root application in Tomcat.
Builds 180, 181, 182, 183 have teh same behaviour for me. Hudson checks out
everything from svn and then just waits. In that situation after clicking the
Red X button (that is supposed to cancel the build) the Hudson build gets
unstuck and continues (without canceling the build).
I had rolled back to 179 and build no longer gets stuck after the svn checkout.
I'm guessing it somehow related to 1244 as I have problems before with "no
changes" builds.
Environments is Solaris 10, Hudson runnning as a root application in Tomcat.
What's the protocol do you use to connect to your server? svn+ssh? http?
When a build gets stuck, can you go to http://server/hudson/threadDump to obtain
the full thread dump (assuming you run this on the master)? I'd like to know
where the build is stuck.
Yes, it's possible.
What's the protocol do you use to connect to your server? svn+ssh? http?
When a build gets stuck, can you go to http://server/hudson/threadDump to obtain
the full thread dump (assuming you run this on the master)? I'd like to know
where the build is stuck.
Activity
jenkins-infra-bot commentedon Feb 12, 2008
Raw content of original comment:
Yes, it's possible.
What's the protocol do you use to connect to your server? svn+ssh? http?
When a build gets stuck, can you go to http://server/hudson/threadDump to obtain
the full thread dump (assuming you run this on the master)? I'd like to know
where the build is stuck.
jenkins-infra-bot commentedon Feb 12, 2008
stanoislav:
Raw content of original comment:
Created an attachment (id=177)
Thread Dump
jenkins-infra-bot commentedon Feb 12, 2008
stanoislav:
Raw content of original comment:
We use https:// to conenct to svn. We have only one Hudson server (no slaves).
jenkins-infra-bot commentedon Feb 12, 2008
stanoislav:
Raw content of original comment:
Created an attachment (id=178)
Thread Dump While using HTTP
jenkins-infra-bot commentedon Feb 12, 2008
stanoislav:
Raw content of original comment:
I have tried switching from https to http and behavior is the same. Pls see
attached second thread dump
jenkins-infra-bot commentedon Jun 16, 2008
Raw content of original comment:
Code changed in hudson
User: : kohsuke
Path:
trunk/www/changelog.html
http://fisheye4.cenqua.com/changelog/hudson/?cs=10148
Log:
[FIXED] I guess JENKINS-1282">
JENKINS-1282is the closest to associate with this RFE.