Abandon scheduled builds that have hung
Hi all,
I have ever Build power going in the permissions tab, I am the uber-super user of my project and I cannot Abandon a scheduled build that has hung. I get a "Not Authorized to abandon the build". Restarting the Jazz Build Engine has no effect, and the RTC Client shows the build engine as still busy.
Any ideas on what I can do?
Cheers
Rich
(http://twitter.com/cumbers)
I have ever Build power going in the permissions tab, I am the uber-super user of my project and I cannot Abandon a scheduled build that has hung. I get a "Not Authorized to abandon the build". Restarting the Jazz Build Engine has no effect, and the RTC Client shows the build engine as still busy.
Any ideas on what I can do?
Cheers
Rich
(http://twitter.com/cumbers)
6 answers
Hi all,
I have ever Build power going in the permissions tab, I am the uber-super user of my project and I cannot Abandon a scheduled build that has hung. I get a "Not Authorized to abandon the build". Restarting the Jazz Build Engine has no effect, and the RTC Client shows the build engine as still busy.
Any ideas on what I can do?
Cheers
Rich
(http://twitter.com/cumbers)
Anyone got a fix for this? We have 2 scheduled builds that are no longer running, but are showing in the eclipse client. When you got to submit a request for a new build, we are told the build engine is busy, but the build engine is not. The build request is serviced immediately. Would love to clear those old failed builds out of my queue!
Just for completeness, does your user have a role with full build-related permissions in the team area? Any user with that kind of role should be able to Abandon a build (among others).
Team Configuration->Permissions->#rolename#->Permitted Actions->Build->Abandon Build (server)
ciao!
Team Configuration->Permissions->#rolename#->Permitted Actions->Build->Abandon Build (server)
ciao!
> the RTC Client shows the build engine as still busy.
This is a known problem. If there are any builds associated with that engine that the server thinks are still in progress, the build engine will appear as busy even though it isn't. We are considering a fix whereby any previous builds associated with the engine are automatically abandoned when jbe is restarted.
This is a known problem. If there are any builds associated with that engine that the server thinks are still in progress, the build engine will appear as busy even though it isn't. We are considering a fix whereby any previous builds associated with the engine are automatically abandoned when jbe is restarted.
> the RTC Client shows the build engine as still busy.
This is a known problem. If there are any builds associated with that engine that the server thinks are still in progress, the build engine will appear as busy even though it isn't. We are considering a fix whereby any previous builds associated with the engine are automatically abandoned when jbe is restarted.
Is there any plan of when this know issue will enter any upgrade? And I suppose need to upgrade both RTC server and client for this?
This is a pain point in our own self-hosting on Build. It's covered by work item 78579: In-progress builds left in in-progress state if build engine restarted and is planned for 3.0 M4 (the current milestone of 3.0). It would be a candidate for back-porting to a 2.0.0.x maintenance release.
I've added a comment to the work item describing how to clean up such builds manually.
I've added a comment to the work item describing how to clean up such builds manually.