There are several "shelly" steps (sh, bat, powershell and pwsh). Of these, bat and powershell don't really need much configuration, because they come with Windows.
Similarly, any Linux will have a 'sh', although there I think it might be useful to be able to specify dash/bash/ksh/csh/... on the step. (And a Windows machine might also have a sh executable.) However, PowerShell Core is multi-platform and installable via zip or tarball. As such, I'd be inclined to want to add a tool installer for it (I already have a crawler script ready for it). The main question is: where to add it? Should I a) file a PR for it on the workflow-durable-task-step-plugin (adding the Downloadable as well as the ToolInstaller), or b) just make it a tiny separate plugin? I'd be more inclined towards a), because it would enable a nice selection of the install to use on the snippet generator for the pwsh step. With b) you'd essentially only have the general tool section entry. Either way, a withPwsh (or withPowerShellCore?) step would also make sense, to put a particular install in PATH for a delimited set of steps (as I understand it, with the tool section, it always applies to an entire stage). -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAKMi--BPf7BXEtgPWbFX6-tX_UCjcz2AUb%3DC_mJrntRWTBr1SA%40mail.gmail.com.
