-
Notifications
You must be signed in to change notification settings - Fork 17
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
Name Powershell Script and Log Files Uniquely #6
Conversation
# | ||
# @return [Hash] :stdout and :stderr | ||
# | ||
# @return [Hash] :stdout and :stderr |
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 was an accident, which reminds I should probably enable RuboCop on this project and add an automated build.
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.
Yup. Fixing.
@sneal - pushed with the fix.
c1f1ada
to
11220fa
Compare
In order to allow winrm-elevated to run concurrently against the same Windows server, name the powershell script uploaded to the server using a randomly generated UUID. In addition, the logfiles generated by the script will be named using the GetTempFileName to ensure uniqueness. We will clean up the logfiles when the script is finished. Since the same script can be uploaded once and invoked multiple times it will be left intact.
11220fa
to
fad4e00
Compare
LGTM. I think we can cross the debugging bridge when we need. Perhaps we look for an environment variable, when set we skip the log deletion. |
👍 yeaah I wouldn't worry about the debug scenario |
tests work on my machine. |
Thanks guys. Will this be 0.3.0? |
yup. released! |
In order to allow winrm-elevated to run concurrently against the
same Windows server, name the powershell script uploaded to the server
using a randomly generated UUID.
In addition, the logfiles generated by the script will be named using the
pid of the script's running process.
We will clean up the logfiles when the script is finished. Since the same
script can be uploaded once and invoked multiple times it will be left intact.
The intent here is to deal with the issue described here: #5
@mwrock @sneal if you could review and possibly merge when possible that would be great.
Open for discussion of course. Thanks!