-
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
Deploy AzureRM Web App task fails because of missing file #3074
Comments
I got same problem. |
Got same problem with 2.1.3. My last successfull deploy used 2.0.7 and was run Wednesday 9th November |
Same issue - looks like the task updated to 2.1.3 at midday today and deployments have all been failing since then. |
Same problem here :/ |
Same problem here. My last successful deploy was 2016-11-11T10:44:27 with 2.1.2 |
Same problem here to |
We have the same issue as well, this is the error we get:
This is the timestamp of the first occurence of this today on our build hosts. |
Same issue for us :/ |
Same here :-( |
Anyway to force it to use 2.1.2? |
We are getting a similar error since 2.1.3 :
|
If you have access to the build server, a temporary workaround is to unzip the task.zip inside the 2.1.3 folder of the AzureRMWebApp task |
same here, really bad timing too. Started happening around 2 hours ago. A release at 11:30 GMT succeded. Redeploying the same release 2hrs ago failed. I can see task.zip. Unzipping this zip file in the 2.1.3 folder did not fix the issue as the folder got cleaned next release. |
Same here |
Same here :(. Opened another issue, which I have cloded now, but same error detailing my configuration can be found here: |
the same!!! |
Same here... |
same, here's a link to a related SO question and a suggested workaround |
same issues as @aadje |
@jakobehn (long time no see ;) Tnx Jacob... that work! |
The work around worked for me. Not sure why it erased for @adonnelly. |
I copied the contents of 2.1.2 inside 2.1.3 and our build worked... |
@alfredodev solution fixed everything |
Sorry what is the fix. How to copy 2.1.2 inside 2.1.3? Is this on VSTS side or something end user have to do? |
Getting this too |
@mravko, what if you are using "Hosted" agente queue? |
Can't help you there. Sorry. Maybe someone else can. |
Appologies for lack of my knowledge. I am on Hosted agent too, Can we create a Default agent? Reading this SO answer Default agent seems to be on premises only or it can be in cloud too? |
Tried the work around. Initially it seemed to be cleaning the directory after each release, but not anymore (maybe I imagined it). Anyway getting a slightly different error now. |
Sorry for the inconvenience we fixed the issue, you should be able to use the task. |
indeed it does. Thanks @mvvsubbu |
Confirmed here! |
Confirmed |
Confirmed here. |
Deploy AzureRM Web App
task fails with version 2.1.3. Some hours ago this task used version 2.1.2 and everything went fine.The text was updated successfully, but these errors were encountered: