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

(BKR-1445) Update Windows agent paths for puppet6 #64

Merged
merged 1 commit into from
Sep 11, 2018

Conversation

caseywilliams
Copy link
Contributor

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.

},
'pwindows' => { #pure windows
'pswindows' => { # pure windows
Copy link
Contributor Author

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

@caseywilliams
Copy link
Contributor Author

PR tests have failed, but it seems unrelated? Actual output is here

@caseywilliams caseywilliams changed the title (WIP) (PA-1923) Update Windows agent paths for puppet6 (PA-1923) Update Windows agent paths for puppet6 Sep 10, 2018
The install locations for puppet-agent in puppet6 have been updated; This
adds the new install locations to the PATH.
@caseywilliams caseywilliams changed the title (PA-1923) Update Windows agent paths for puppet6 (BKR-1445) Update Windows agent paths for puppet6 Sep 11, 2018
Copy link
Contributor

@kevpl kevpl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm 👍

@kevpl
Copy link
Contributor

kevpl commented Sep 11, 2018

The stderr: fatal: reference is not a tree failure is a transient we see on occasion, perhaps because of force pushing repos around. Usually re-kicking takes care of it.

Jenkins, retest this please

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