-
Notifications
You must be signed in to change notification settings - Fork 24
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
Issue with additionalArguments #26
Comments
Hi Alan, |
Also an issue for us, we cannot use this tool without providing additional arguments! Is this abandonware?? |
I ended up using the PowerShell locally with the bug fix and some updates
to fit my needs...
Le mar. 17 mai 2022, 07 h 19, p3365 ***@***.***> a écrit :
… Also an issue for us, we cannot use this tool without providing additional
arguments! Is this abandonware??
—
Reply to this email directly, view it on GitHub
<#26 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANKEFFWKEZAZPZJS5KHZHFTVKN6F3ANCNFSM4I253F6A>
.
You are receiving this because you authored the thread.Message ID:
***@***.***
com>
|
Hi, maybe there were any updates for that issue, tried all possible options to add a second argument. All unsuccessful |
No changes in this repo for 5 years. It seems like the author abandoned it. |
Hi !
Since the "Migrate task to latest vsts runner" commit in August, the additionalArguments input is passed to the command line between double quotes.
While running in VS2017 Hosted Agent, it now fails if you pass more than 1 extra argument.
The text was updated successfully, but these errors were encountered: