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

Prevent invalid idleMinutes in retention strategy #623

Merged
merged 1 commit into from
Feb 22, 2018

Conversation

pjdarton
Copy link
Member

The DockerOnceRetentionStrategy class changed the name of the field in which it stored the "timeout" value. This resulted in some folks finding it had become zero, and this caused the plugin to close containers "due to inactivity" before they had a chance to become active.
This change ensures that, in the event of an invalid value being provided, the class will use the default value (10 minutes), and also ensures that, from this point onwards, the value persisted is the value read (previously there was a discrepancy).

The DockerOnceRetentionStrategy class changed the name of the field in
which it stored the "timeout" value.  This resulted in a lot of folks
finding it had become zero, and this caused the plugin to close
containers "due to inactivity" before they had a chance to become
active.
This change ensures that, in the event of an invalid value being
provided, the class will use the default value (10 minutes), and also
ensures that, from this point onwards, the value persisted is the value
read (previously there was a discrepancy).
@ndeloof ndeloof merged commit 0fd675a into jenkinsci:master Feb 22, 2018
@pjdarton pjdarton deleted the fix-zero-idle-time branch March 6, 2018 18:38
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

Successfully merging this pull request may close these issues.

2 participants