-
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
AzureRmWebAppDeploymentV4 v.4.2.2 tempParameterSet.xml etr #7784
Comments
@mbialitskiy , thanks for reporting the issue. This is a genuine issue and will be fixed. |
@mbialitskiy , the issue is fixed and the fix will be available in upcoming deployment. |
@vincentdass does this fix the issue with appsetting json variables not being replaced as well? |
@vincentdass also when is the upcoming deployment? Is there a way to see a schedule of this? |
@joe45sp , JSON var. substitution issue is getting hotfixed. This should available this week. |
@vincentdass is there anyway to see release progress? Also, can you point me to the commit that fixed the json var substitution? Just curious to see what fixed it. Thank you for all your help with this!!! |
@joe45sp , JSON variable substitution fix: #7818. (Task replaced the values in JSON but deployed the unmodified (original) package and this created an impression that JSON variable substitution didn't work). |
Environment
VSTS:
account name: rapmd
team project name:rapmd
release definition name: QA
release definition number: 248+
Agent:
Private (windows 2016, agent ver.2.120.2)
Issue Description
The error appeared after extension update from version 4.1.12 to 4.2.2
In release I have two successive tasks: deply webapp and function app.
After first is successfully deployed the second fails with error:
Error: Failed cp: cp: dest file already exists: C:\agent3_work\r1\a\tempSetParameters.xml
If switch tasks the result is the same.
The workaround for now is to create a step between tasks that removes the tempSetParameters.xml but I think it should be fixed in the service.
Error logs
2 Logs: 4.1.2 - with success deployment, 4.2.2 - with error
4.2.2.log
4.1.2.log
The text was updated successfully, but these errors were encountered: