-
Notifications
You must be signed in to change notification settings - Fork 8
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
Dynamic "Keep around minutes" according to Hetzner's hourly billing cycle #30
Comments
Hi @sandrinr, thanks for interesting idea. I can see 2 potential issues here:
This could lead in theory to consistent over-billing by one hour. So we would probably need some time buffer before whole hour is wrapped. |
With latest release you can now specify 2 different ways of how agent is shutdown. Second option will shutdown agent just before billing cycle completes: As mentioned in comment above, there is safety buffer of 5 minutes. @sandrinr looking forward for feedback 😉 |
Thanks a lot @rkosegi for providing this feature so quickly! Looking at our cloud statistics after the upgrade pretty much shows what I would expect. |
What feature do you want to see added?
This is a request for an optimization around how Jenkins manages spawned Hetzner server resources. Currently, the plugin lets idle resources stay around for a configurable amount of time of which the default is 10 minutes. This can lead to the situation where multiple nodes are created and torn down within the same hour.
Hetzner bills its server resources on a hourly basis. The customer pays for every started hour. Jenkins normally does not know about the potential future workload it has to cope with. By letting nodes run idle just before a new hour would be started, Jenkins could make maximum use out of the already spawned resources.
Upstream changes
No response
The text was updated successfully, but these errors were encountered: