Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Re"activate" agents when more work has to be done #157

Closed
anbraten opened this issue Jun 30, 2024 · 1 comment · Fixed by #163
Closed

Re"activate" agents when more work has to be done #157

anbraten opened this issue Jun 30, 2024 · 1 comment · Fixed by #163

Comments

@anbraten
Copy link
Member

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.
@anbraten anbraten mentioned this issue Jul 2, 2024
Merged
@pat-s
Copy link
Contributor

pat-s commented Jul 6, 2024

I came across this just now

image

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.

Happy to test!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Reactivate agents and prevent draining recently active agents woodpecker-ci/autoscaler
2 participants
@anbraten @pat-s