-
-
Notifications
You must be signed in to change notification settings - Fork 477
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CI Test against PowerShell 5.1 #794
Comments
I'm not sure if I understand what is a subject of your request. Would you like extend continues integration tests of Pester to PowerShell v. 5.0.10586.51 also? |
@it-praktyk The other way around: I would like to extend the coninuous integration tests of Pester to PowerShell 5.1. Currently the latest seems to be 5.0.10586.51. |
Yes, exactly I thought about that - means test Pester with/under new version of PowerShell. IMHO, extending CI workflow is not needed before publishing v.4 RTM - probably most of use use this version on development machines. The person who can do it is @dlwyatt but I think that his knowledge/time/involvement is more required for other tasks. |
I patched the build agents today; it's running 5.1 now. |
I'm guessing that the CI server is probably using PowerShell 5.0.10586.51 for the v5 tests. I'm inferring this from the ToolFoundations project whose CI is on the same server. From the admin pages of that project I have not found any signs of PowerShell 5.1. (I'm a TeamCity noob, so I apologize if I have this wrong.)
It seems like at least late version(s) Pester should be tested against PowerShell 5.1.
The text was updated successfully, but these errors were encountered: