-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
[PowerShellV2] Allow to use alternative execution operator #14613
[PowerShellV2] Allow to use alternative execution operator #14613
Conversation
Do we have e2e tests for this case? |
For new input there no e2e, but I've created a ticket to add them. |
* Renamed input * Changed text of helpmarkdown
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested these changes manually, found no issues
* Fixed EOL * Chnaged label of input
LGTM, thanks! Let's merge it once we have e2e tests for new input and plan this for the near time. |
https://github.com/microsoft/azure-pipelines-tasks into users/EzzhevNikita/powershell-allow-use-call-operator
Task name: PowerShellV2
Description: Added optional parameter that allows PowerShell task to execute the script using call operator (&) instead of default dot sourcing operator. This was added to address the issue from feedback ticket
Documentation changes required: (Y/N) Y
Added unit tests: (Y/N) Y
Attached related issue: (Y/N) feedback ticket
Checklist: