Yes, I believe that's the case. Not the x86 one. Using the -ExecutionPolicy
did the trick from a Jenkins Job perspective.
On Thu, Dec 13, 2012 at 1:32 PM, bearrito wrote:
> Two things.
>
> 1. Windows machines have a 32bit and 64bit powershell.
> 2. Jenkins will typically run on the 32-bit JVM whi
Two things.
1. Windows machines have a 32bit and 64bit powershell.
2. Jenkins will typically run on the 32-bit JVM which means when it invokes
powershell it will invoke the 32bit version.
It sounds like you have Set-Execution Policy on the 64bit version but not
32bit.
You might want to config
This is helpful:
http://jenkins.361315.n4.nabble.com/PowerShell-plug-in-question-td1468725.html
After that it's the usual troubleshooting script issues from different
runtime contexts.
On Thursday, December 13, 2012 1:06:13 PM UTC-6, mwpowellhtx wrote:
>
> Hello,
>
> We've got some Windows Powe
Hello,
We've got some Windows PowerShell scripts I would like to expose throughout
our jobs for natural house keeping steps.
I've got the Set-ExecutionPolicy set appropriately and I can run scripts
apart from Jenkins through the command line, with PowerShell (i.e. context
menu), etc.
Running
