The official Docker documentation says:
Docker recognizes certs stored under Trust Root Certification
Authorities or Intermediate Certification Authorities.
That is, you can proceed as the following:
Start > "Manage Computer Certificates" (also available in the control
Right-click on "Trusted Root Certification Authoritites" >
"All tasks" > "...
I think the time and effort it will take to set up another tool that performs this type of work will be about the same as it would be to setup Jenkins. If you are looking into a different tool though, I would checkout Rundeck. It is a great tool for creating scripts and allowing other privileged users to execute them. I'm not sure if it will meet your needs ...
Your python problem is the \n after the commands, write already append a newline, so your script does the following:
$cred = Get-Credential # Start the command
# This line is ignored as extraneous after Get-Credential, but you can see it in your output.
Administrator # Send proprely to the User: prompt
# Sent to the Password: prompt
Password # Send to the ...
You should probably create an Ansible issue for this as it's most likely a bug in Ansible.
The first error makes me think about WinRM pipelining:
Ansible 2.3.0 introduced an always-on WinRM pipelining feature (similar to SSH pipelining), and that may be behind this.
SSH pipelining can cause issues in Ansible for Linux, and it can be useful to turn it off,...
If it's an Intel CPU, you may have to enable Intel VT-x in the bios. Sometimes the virtual machine will tell you this, and sometimes not. Here's a link that might help (ignore the Windows 10 part since you're on Win7). Also getting everything to the newest version would be a good idea if you can.
I'm guessing that your PowerShell script is hanging because of the Invoke-Command command. My best guess is PowerShell is either prompting you for something, you are passing in an argument incorrectly, or you are executing the script in your script block incorrectly. I'm not sure exactly how Script-Block works when referencing paths to PowerShell scripts, ...
The conflict is occurring between ngc and webpack. When rimraf aot && ngc -p ./tsconfig-aot.json is moved to its own script and executed prior to test and build:prod:aot then running test and build:prod:aot with npm-run-all will work as expected.
Also, running with PowerShell is not necessarily a good idea since it interprets some of the output ...