-
Notifications
You must be signed in to change notification settings - Fork 325
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
(BKR-1168) Exit early on --version, --help, and --parse-only #1523
Conversation
Those failures are the continued Windows cURL issues. Everything else is good. |
Jenkins, test this please |
1 similar comment
Jenkins, test this please |
Pending removal of further early-exit conditions based on |
Jenkins, retest this please. |
Previous "dry-run"-esque behavior was leaky, resulting in a not-so-dry run. - Subcommand spec tests for exec should not actually call cli.execute!, so intercept them. - Process all early-exit flags first
Jenkins, retest this please. |
@kevpl Tests are all pass except for a transient package error on Solaris. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm 👍
CHANGELOG.md
Outdated
@@ -19,6 +19,7 @@ git logs & PR history. | |||
|
|||
- Raise `ArgumentError` when passing `role = nil` to `only_host_with_role()` or `find_at_most_one_host_with_role()` | |||
- Use `install_package_with_rpm` in `add_el_extras` | |||
- Exit early on --help/--version/--parse-only arguments instead of partial dry-run |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks like this line has been pushed down into 3.36.0 with the new release, so this will have to be put back up into the Unreleased section
looks like a vmpooler provisioning issue, will rekick. Jenkins, test this please |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm 👍
Previously, some code paths could allow continued execution of Beaker after encountering these flags. This resulted in a not-so-dry run scenario which, at best, caused confusing error output when
beaker --version
was called and, at worst, may have led to the unintentional execution of a configured provisioning task.