-
-
Notifications
You must be signed in to change notification settings - Fork 51
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
Add a check on windows part, to exec commands on a non cygwin environment #77
Add a check on windows part, to exec commands on a non cygwin environment #77
Conversation
Can one of the admins verify this patch? |
Thanks for your contribution! I would suggest putting both alternatives into the if like this:
That cleans up that a little bit. Also adjusting the comment at https://github.com/puppetlabs/beaker-rspec/pull/77/files#diff-befb1733680f635c46fc0aad3de0ba18R248 would be good. |
Cleaned up a little bit. Humm, thinking a little bit, should we change the class name from BeakerCygwin to something more descriptive like, BeakerWindows? |
Renaming the class sounds like a good idea, now that it's not cygwin specific. I hope that nothing depends on the class name. |
@puppetlabs-jenkins test this please |
Refer to this link for build results (access rights to CI server needed): |
…-node Add a check on windows part, to exec commands on a non cygwin environment
* No longer need to use fork! Work has been pushed upstream properly * Update sync file with changes * Bump to 5.4.0 beaker-rspec to fix Powershell issue (voxpupuli/beaker-rspec#77)
* No longer need to use fork! Work has been pushed upstream properly * Update sync file with changes * Bump to 5.4.0 beaker-rspec to fix Powershell issue (voxpupuli/beaker-rspec#77)
* No longer need to use fork! Work has been pushed upstream properly * Update sync file with changes * Bump to 5.4.0 beaker-rspec to fix Powershell issue (voxpupuli/beaker-rspec#77)
When a PSwindows node neither rm nor /dev/null will work. This is a way to fix this (probably not the best one...)