-
Notifications
You must be signed in to change notification settings - Fork 867
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
[BUG]: passing a password with a "&" break --unattended install #4787
Comments
Hi @JJKW1984 thanks for reporting! We are working on more prioritized issues at the moment, but will get back to this one soon. |
This is not just .\config.cmd --unattended --url https://dev.azure.com/AareonRelionGmbH --auth pat --token xxx --projectName "xxx" --agent "xxx" --windowsLog
onAccount "xxx" --windowsLogonPassword 'xxx' --runAsService --deploymentGroup --deploymentGroupName "xxx" --addDeploymentGroupTags --deploymentGroupTags 'Serverinstance, Secondary, Production, Host' Results in a registered Agent (in Azure DevOps) with only one tag |
the config.cmd is pretty old https://github.com/microsoft/azure-pipelines-agent/blob/master/src/Misc/layoutroot/config.cmd (ca. 5 years not touched) I usually call the exe directly |
This issue has had no activity in 180 days. Please comment if it is not actually stale |
What happened?
When creating a unattended install script we are unable to pass any password with a "&" starting it.
.\config.cmd --unattended --agent 'agent1' --pool 'build pool' --url 'https://dev.azure.com/testorg' --auth 'PAT' --token 'token' --runAsService --windowsLogonAccount 'US\ADO' --windowsLogonPassword '$password'
We have tried escaping the password and passing it in as a variable but the command misinterpreted as two commands.
Versions
Windows 2022 / 3.328.0
Environment type (Please select at least one enviroment where you face this issue)
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
No response
Version controll system
No response
Relevant log output
The text was updated successfully, but these errors were encountered: