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.
What's this PR do?
Upgrades beaker to 6, kicks off a release (3.2 -> 3.3)
Any background context you want to provide?
As part of the beaker 6 upgrade for pe_acceptance_tests, I had to bump the version on beaker-pe. My local testing of pe_acceptance_tests pointed at my local directory for beaker-pe, so I verified this works.
Details of my test:
In pe_acceptance_tests, locally, I pointed beaker-pe at my local directory (mentioned above), then pointed at beaker-puppet 4.0 (to get the beaker 6 transitive deps worked out).
Then I visited this CI run and yoinked a set of commands to run locally:
pe_ver
andpe_dir
for the hosts.cfgThe
bundle exec beaker exec
command completed with a return value of 0, all tests passing.