Improve support for ToolInstallation - #34
Conversation
84a840c to
d8228d6
Compare
|
Can we get a review on this please? This is something our team needs as well. Is there an new issue somewhere we can ping people on? |
While you are waiting for a review, you can install the pre-release build, use it, and report your results with it. That will help you by confirming that it solves your immediate problem and it will help the maintainer because they will know that one other user has confirmed it works for them. |
|
I would like someone else to validate this PR. If no one does it, I will merge it in a few weeks. |
d8228d6 to
4c5ef77
Compare
555cc1b to
0e4cbad
Compare
JENKINS-68052 Improve powershell version selection JENKINS-76152 The powershell path is wrong when using a custom powershell release from a freestyle job
0e4cbad to
93f0e63
Compare
|
Some of my Windows builds are now failing with: I have two installations defined: |
|
Can you share your powershell installations config file
Yes, that was the idea.
any particular thing missing? pull requests are always welcome |
|
This update is broken, like completely. No Powershell steps works in any of my projects. This is a simple step with just $PSVersionTableIt's pretty obviously something in the path as pwsh is getting appended to the pwsh.exe path. OS: Windows Server 2025 The plugin xml file contains this |
|
@ViperTG Check the HOME configuration of your PowerShell tools. It’s probably set to the path to the PowerShell executable. It should set to the directory of the PowerShell executable. Or, if PowerShell is in PATH, left empty. |
|
@ViperTG while trying to parse old configs, missed when someone changed the default installations. Just released #47 in release https://github.com/jenkinsci/powershell-plugin/releases/tag/185.v7a_026da_c54ee |
Yep work fine now, thanks. |
Of course, sorry for the delayed reply
OK!
I mean, a minor update broke everything. If the release notes at least contain a "BREAKING: you now need to define new installations with names DefaultWindowsPwsh ,etc etc" that'd have been enough for me. I see it's fixed now, thanks a lot everybody. Will update soon and report back if needed. |
This plugin is now using continuous delivery #42. It no longer uses Semantic Versioning, so there are no major or minor changes. It was not supposed to be a breaking change. But making code changes to work with old persisted changes is hard, and that is why this pull request was open for several weeks awaiting feedback. |
|
Thanks for all the hard work, I really appreciate your plugin and open source software. |


Better handling for ToolInstallation to use custom installations, behind defaults for Windows and Linux.
Testing done
Submitter checklist
Link to relevant pull requests, esp. upstream and downstream changesEnsure you have provided tests that demonstrate the feature works or the issue is fixed