-
Notifications
You must be signed in to change notification settings - Fork 66
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-1445) Update Windows agent paths for puppet6 #64
Conversation
}, | ||
'pwindows' => { #pure windows | ||
'pswindows' => { # pure windows |
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.
I kept seeing 'pswindows'
instead of 'pwindows'
elsewhere, so I've updated this to match -- please let me know if I'm wrong here
5a7affc
to
0582962
Compare
PR tests have failed, but it seems unrelated? Actual output is here |
0582962
to
d557ad8
Compare
The install locations for puppet-agent in puppet6 have been updated; This adds the new install locations to the PATH.
d557ad8
to
3334f75
Compare
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 👍
The Jenkins, retest this please |
In PA-1923, we're updating install paths in Windows agents so that they more closely match the paths used in *nix agents -- this PR adds the new location of the vendored ruby executable to the default PATHs set up by beaker while installing puppet-agent. We could make this distinction based on the collection name, but it seemed less disruptive to just include all the possible paths at once.
The pathing work hasn't been merged in puppet-agent yet (the PR is here), so I'm putting the blocked label on this PR for the moment while I finish testing everything there.