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.

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

What is the difference between WOODPECKER_AGENT_INACTIVITY_TIMEOUT and WOODPECKER_AGENT_IDLE_TIMEOUT? #164

Open
pat-s opened this issue Jul 6, 2024 · 1 comment

Comments

@pat-s
Copy link
Contributor

pat-s commented Jul 6, 2024

There is also WOODPECKER_AGENT_ALLOWED_STARTUP_TIME which is an alias for WOODPECKER_AGENT_INACTIVITY_TIMEOUT.

@anbraten
Copy link
Member

anbraten commented Jul 6, 2024

WOODPECKER_AGENT_INACTIVITY_TIMEOUT is the timeout used to mark an agent for removal as it hasn't connected for a while (or not at all like an error in the config). Startup time is an old setting which was pretty confusing to me and is now kept to be at least somehow backwards compatible.

Only agents that have been inactive for the duration defined by WOODPECKER_AGENT_IDLE_TIMEOUT will be marked for removal. This way we don't remove agents immediately if they haven't been used for a short amount of time.

@lukashass also noted that the settings should be explained / improved in #162 (comment).

There is also the idea in #73 (comment) to support some kind of removal window so in case of providers like Hetzner an angent is removed at the end of an hour only or kept for another one to maximise cost efficiency. However I am not sure how to implement that in a generic way.

PRs and suggestions how we could document or implement those parts are highly appreciated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants