-
Notifications
You must be signed in to change notification settings - Fork 82
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
Minimum node life time. #356
Comments
What happens if you do both:
? Is it still removed by jenkins after some time? |
Hi Michał, I need to remove the node after idle, but I want the possibility to set minimum work time for nodes. |
Why not setting idle 25h? Isn't that effectively the same?
…On Mon, Jan 16, 2023, 09:18 yury-tyumin ***@***.***> wrote:
Hi Michał,
I need to remove the node after idle, but I want the possibility to set
minimum work time for nodes.
Example:
I want 1h idle for nodes, but the new node to work a minimum 24h, after
that it can shutdown after 1h idle.
—
Reply to this email directly, view it on GitHub
<#356 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABF4AJCOJSEKETNPTTLLGE3WST747ANCNFSM6AAAAAATQVH4TA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
it's not the same. |
Ability to set the time during which the node will not turn off, despite Idle.
This will helpful for Mac OS nodes. Mac dedicated hosts require a 24-hour minimum allocation period, adhering to the macOS Software Licensing Agreement (SLA) before they can be released.
This will allow doesn't to turn off the node unnecessarily and solve related problems.
The text was updated successfully, but these errors were encountered: