Repository navigation
Release 0.14.8 - #1217
Merged
Merged
Release 0.14.8#1217
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
0.14.8 adds host resource limits for agent sessions: with
[resources]set in the User config,thirdshiftwaits for enough available memory and low enough CPU load before it starts a session (#1206).thirdshift resources [--json]shows the host's measurements, the configured limits and the admission decision. The same view is on the Console's new Resources page (9org e) (Gate agent sessions on configurable host resources #1206).0disables each limit, and both default to disabled. Resumes, Repairs, Security reviews, release summaries and preflight Model test calls also wait at the gate. Configured limits delay new sessions but don't stop running ones (Gate agent sessions on configurable host resources #1206).email-unless-merged [<address>](or--email-unless-merged), oremail.unless_merged = truein the User config, emails a Run notification only when the Command did not end merged. A merged Security fix that still leaves a finding open, or has findings waiting for the Day shift, is still emailed. The notification is always saved beside the Command log. The email-flag conflict error now reads "email, email-unless-merged and no-email can't be used together" (Email a Run notification only when the Command did not end merged #1201).Also: README and docs updates, with Console setup moved into the manual (#1202).
Version diff