jason - 28/Jul/08 11:08 PM Hi Stephen, I guess you are talking about the status box on the project homepage? If so: 1) There may be multiple agents involved in a single project build, and in upcoming Pulse versions there may be multiple builds running for a single project. For this reason the processing agent is displayed for each stage in the build summary tables, rather than at the top level. There are, however, places where we could add more information about which agent is running what, e.g. on the agents tab, on the agent status view, and in more detail on the server activity tab. 2) As the status box is connected to the project, rather than a single build, I don't think we can put a cancel button there. The pause button pauses the project (so it will ignore subsequent triggers) rather than any build. However I agree that the location of the cancel button is not convenient - you should be able to cancel from the build summary page at the very least, and possibly in other places. We will use this issue to tack adding links to cancel to the build views.

Stephen Nesbitt - 28/Jul/08 11:16 PM Yes, you are correct. I see your point and mostly agree with it. The use case I am working with against is that I manually trigger a build (or a user asks me to kill a build). Therefore I have a project and a build number. There should be some way that I can easily tell Pulse, please kill build 18 - no matter what stage - on Project Foo. And regards the pause, the fact that a project with a paused build ignores all triggers - including manual invocation - is a bit confusing. Or I found it so ;-) as i kept trying to manually invoke a build only to have it do nothing. I really don't have a solution, just a data point. Man, I really don't envy you on this project. A lot of very tough nuts to crack (which you are dealing nicely with. Still...) -steve

jason - 08/Aug/08 12:27 AM Done in change 4673.