Your browser was unable to load all of the resources. They may
have been blocked by your firewall, proxy or browser configuration.
Press Ctrl+F5 or Ctrl+Shift+R to have your browser try again.
I got into a situation where my SVN URL was bad so that when I requested a build, it took about 5 minutes for an error to show up as it was, I guess, waiting for a timeout on SVN. During that 5 minutes, I didn't even know a build was happening or going to happen. I remember that a build was requested as the yellow bar appeared right after I triggered it. But after that, there is nothing in the system log that really helps, and there is nothing in the queue.
I then fixed my SVN URL and have triggered another one, but now I see no change to the system log and again nothing in the queue. So now I don't know what is going on. Did I get another error but can't see it, is it hung, etc.? The last thing I see in the system log (12 minutes ago) is:
2009-07-12 01:24:04,7 [Thread-9296] INFO com.pmease.quickbuild.plugin.scm.svn.SvnRepository - Determining head revision for repository: svn
I think you should add something to the Queue tab to show running builds, waiting builds, and requested builds. That would also allow me to kill any requested build before it starts.
The only thing I can think of is to stop and restart the server.
-
replies
3
-
views
1950
-
stars
0
-
When a build is requested, QuickBuild tries to determine SVN head revision to build against. After that, the build will be generated and stamped with that revision, and put into queue for a worker thread to pick it up and run.
If the svn url is incorrect, QuickBuild will stuck on the "Determining head revision" phase as you see from the log. However, normally it should not take that long to fail, and once the url is fixed, subsequent triggering will work normally. I intensionally specified non-existent ip address, and incorrect host name as part of the url, and in both case, the configuration are failed with proper error messages in 30 seconds.
I would like to ask below questions:
1. what subversion client are you using?
2. on which platform you've observed this behavior?
3. how bad is that url (I mean actual value of the bad url, <!-- s:) --><img src="{SMILIES_PATH}/icon_smile.gif" alt=":)" title="Smile" /><!-- s:) -->)
Thanks
Robin
1. CollabNet certified binary 1.5.5
2. linux x86-64
3. URL was specified as http://server.src.domain.com/svn/module ... h_A/subdir
I tested under linux, and the "svn info" command reports error only after several seconds. Can you please run the "svn info" command with the bad url in your environment to see how long it takes to report back an error and what the exact error reported?
OTOH, the ability to queue build requests so that they can be stopped/cancelled does make sense, and I've filed an imrovment request as: http://jira.pmease.com/browse/QB-425
Thanks
