On Fri, May 21, 2021 at 5:51 PM Tim Van Holder <[email protected]> wrote:
> 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 > The `ToolInstallation` system is generally deprecated. Modern CI setups are expected to use VMs or containers with appropriate tools preinstalled. So I would probably recommend creating a separate plugin for the likely small number of users who would benefit. Or better yet, just check whether the existing plugin <https://github.com/jenkinsci/powershell-plugin/blob/master/src/main/java/hudson/plugins/powershell/PowerShellInstallation.java> works for you. > 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) > There is limited flexibility in Declarative syntax. For Scripted syntax, this just sounds like it would be better covered by the general JENKINS-28718 <https://issues.jenkins.io/browse/JENKINS-28718>. A dedicated block-scoped step makes sense for logic that does something more complicated than bind a `ToolInstallation` to a `$PATH` entry. -- 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/CANfRfr2Q66ArFPTDY2V8eeQn3t4AR_8giQc%3DtsptoDX5n5e8aQ%40mail.gmail.com.
