Queue status: blocked builds are shown as erroneous

[GoogleCodeExporter]

We have the following issue with v0.8 of the HTT: We have Hudson with 
multiple interdependent projects which trigger each other. It happens often 
that e.g. Project A is already being build, but then Project B finishes and 
triggers a new build of Project A which is added to the queue.

http://hudson.test.net/queue/api/xml delivers then:
<blocked>true</blocked>
<buildable>false</buildable>
<stuck>false</stuck>

HTT shows the build immediately in red as if it were a problem. But I would 
say that "blocked" build is OK since it will start as soon the previous build 
of the same project finishes. What is a problem, is when the build is 
"stuck" (Hudson seems to support this idea as well since only stuck builds are 
marked red and blocked not)

Is it possible to show only "stuck" builds as erroneous or if it is not 
acceptable in some cases, is it possible to configure (either GUI or using a 
property file) which of the queue status shall be shown as erroneous?

Original issue reported on code.google.com by giter...@gmail.com on 24 Mar 2009 at 3:43

[GoogleCodeExporter]

It is indeed anoying. Please try v0.8.1. I no longer make a difference for 
"blocked"
projects. Perhaps we should make them as "build in progress". What do you think?

Original comment by Alexis.S...@gmail.com on 24 Mar 2009 at 4:26

• Changed state: Started

[GoogleCodeExporter]

v0.8.1 solved the issue. Thanx.

yes, "in progress" is OK or maybe add one more status "queued" (for all jobs 
which are 
in the queue but not being build now; "being build" has higher priority than 
"in the 
queue"). But the priority of this feature is not so high I would say.

Thank you once more for the quick response.

Original comment by giter...@gmail.com on 24 Mar 2009 at 7:11

[GoogleCodeExporter]

OK, I will mark it "fixed" for the moment. Thanks.

Original comment by Alexis.S...@gmail.com on 24 Mar 2009 at 8:27

• Changed state: Fixed