Change in disabled agent behavior

I've just begun using Calcutta (good stuff btw). One change that I noticed is in how disabled agents behave. In v. 3 when you disable an agent you can still target specific builds to it and have them run. But with v. 4 when an agent is disabled it is truly disabled. While I see the value of being able to shut down an agent I found the ability to isolate an agent really useful (for setting up new builds or creating a fast lane for some immediate needs).

Was this change intentional? If so, any chance of getting an option to allow the previous behavior?

Thanks,
Tom

2 comments
Comment actions Permalink

Hello Tom,

In fact, you still should be able to run a build on disabled build agent. In run dialog, the first combo-box must allow to select disabled
agent as a target for the build.

Otherwise, you've encountered a bug (probably already fixed one; I've just checked - works nice for me).

Kind regards,
KIR

0
Comment actions Permalink

Good morning,

I think this was user error. When setting up my builds I had capped a bunch of them by setting the "Limit the number of simultaneously running builds" to 1. When I tried to trigger a build against an agent that was disabled I assumed that it didn't run because the agent was disabled. Apparently it was because of the cap.

Thanks,
Tom

0

Please sign in to leave a comment.