Skip to content
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.

Sign up for GitHub

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

Jump to bottom

v9 of the task to may import Pester v5 on a box with it installed #33

Open
kilasuit opened this issue Jun 10, 2020 · 0 comments
Open

v9 of the task to may import Pester v5 on a box with it installed #33

kilasuit opened this issue Jun 10, 2020 · 0 comments

Comments

@kilasuit
Copy link

I noticed this in recent troubleshooting of an internal issue on our build boxes (we don't use the hosted agents)
Seems that this default value

AzureDevOpsExtension/Extension/PesterTask/PesterV9/Pester.ps1

Line 43 in a44ff1d

[string]$TargetPesterVersion = "latest"

will then have an impact on potentially importing pester at this point

AzureDevOpsExtension/Extension/PesterTask/PesterV9/Pester.ps1

Line 61 in a44ff1d

Import-Pester -Version $TargetPesterVersion

I propose to fix this with some additional defensive coding just to be sure that Pester v5 will never accidentally import
kilasuit added a commit to blackmarble/AzureDevOpsExtension that referenced this issue Jun 10, 2020
@kilasuit
Added defensive coding and warning - fixes pester#33
ed5a1ac
@kilasuit kilasuit mentioned this issue Jun 10, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kilasuit