...

• Last but not least a PowerShell® script can be executed from a file that has to be located by the executing Agent:

  Code Block
  language bash title Example how to run PowerShell® script code from a file linenumbers true
  pwsh -NoLogo -NonInteractive -File some_powershell_script.ps1

Windows

The pwsh.exe process is the new name for PowerShell Core starting with version 6.0. The executable changed names from powershell.exe to pwsh.exe. Therefore if using a version < 6.0 please change pwsh.exe to powershell.exe

e.g. @@findstr/v "^@@f.*&" "%~f0"|powershell.exe -&goto:eof

• Find the below examples for download (.json upload): run-powershell-windows.workflow.json

• In order to directly run PowerShell® script code from a JS7 shell job script the recommended approach is to use a shebang replacement like this:

  Code Block
  language bash title Example how run PowerShell® script code with a shebang replacement linenumbers true
  @@findstr/v "^@@f.*&" "%~f0"|pwsh.exe -&goto:eof Write-Output "Hello" Write-Output "world"

  Explanation:

  • Credits for the shebang replacement to How to run a PowerShell script within a Windows batch file
  • If you consider this shebang replacement somewhat cryptic then add it to JS7 - Script Includes which are easily referenced from shell jobs, e.g. by using ##!include pwsh
  • The PowerShell® pwsh.exe executable is available starting with PowerShell 6.0. PowerShell releases 5.x use the executable powershell.exe that that can be used with the shebang accordingly. 

    Therefore if using a version < 6.0 please change pwsh.exe to powershell.exe

    e.g. @@findstr/v "^@@f.*&" "%~f0"|powershell.exe -&goto:eof

• As a bad alternative the PowerShell® executable can be invoked directly and can be parameterized like this:

  Code Block
  language bash title Example how to run PowerShell® script code from a single line linenumbers true
  pwsh.exe -NoLogo -NonInteractive -Command "& { Echo ""Flight Destination: $env:FLIGHT_DESTINATION""; Echo ""Booking Code: $env:BOOKING_CODE""; }"

  Explanation:

  • Consider the quoting: when using the -Command parameter then the PowerShell® script has to be specified from a string. This includes:
    
    • quoting the script by double quotes.
    • quoting code inside the script with two double quotes or using single quotes.
  • Note that each PowerShell® command has to be terminated with a semicolon.

    
    

...