Currently we set NoSchedule to true when an agent isn't needed anymore. In the time it is still processing pipelines, new work could come up, but the agent would not be set to NoSchedule=false again. Instead it is removed and a new agent is spawned afterwards.
Because I had set WOODPECKER_MAX_AGENTS, I also had to wait until the first build was done even though there were plenty of resources available on the active node.
Currently we set
NoSchedule
totrue
when an agent isn't needed anymore. In the time it is still processing pipelines, new work could come up, but the agent would not be set toNoSchedule=false
again. Instead it is removed and a new agent is spawned afterwards.