Rename PowerShell binary on Linux/macOS to pwsh #9
Conversation
|
OK I've created an associated issue for this PR - https://issues.jenkins-ci.org/browse/JENKINS-49443 |
|
I would use this right now if it was available! |
|
Looks great. Sorry for the delay in getting to this. |
|
@chrisalbrecht I've seen that this was merged but there was no release associated with it. |
|
Is there a way to get this working on my Jenkins installation running on MacOS? On the plugin site and on the wiki I see only older versions but it seems there might be an updated variant that might work with PowerShell Core? Sorry if I got this wrong, Jenkins is quite new for me |
|
what is the status on this? our jenkins install has the latest code for the powershell plugin but everything still runs under ps 5. |
|
Hmmm. It looks like the change was merged but never released. |
|
@chrisalbrecht Will you be able to do a release? |
|
Any status on this? |
|
@duemir @iandrewdunn I don't have my dev environment set up to do a release at the moment, I tried pinging @damienfinck to see if he can - but I haven't heard back. I'll try to find a bit of time this week to get everything up and running to release. |
Several months back the PowerShell team renamed the binary for PowerShell Core to
pwshon Linux and macOS andpwsh.exeon Windows. I believe when running on Windows systems, we want to continue to use Windows PowerShell (powershell.exe) as the default. However if there was a way the user could choose between pwsh.exe and powershell.exe on Windows, that would be really useful. Neither is a full superset of the other - each has unique functionality.We should also consider renaming the plugin from
Windows PowerShellto justPowerShell. See https://blogs.msdn.microsoft.com/powershell/2017/07/14/powershell-6-0-roadmap-coreclr-backwards-compatibility-and-more/ for more info on PowerShell editions.