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.
2016-11-11T13:25:14.8013148Z ##[section]Starting: Deploy AzureRM Web App:
2016-11-11T13:25:14.8522053Z ==============================================================================
2016-11-11T13:25:14.8522053Z Task : Azure App Service Deploy
2016-11-11T13:25:14.8522053Z Description : Update Azure App Service using Web Deploy / Kudu REST APIs
2016-11-11T13:25:14.8522053Z Version : 2.1.3
2016-11-11T13:25:14.8522053Z Author : Microsoft Corporation
2016-11-11T13:25:14.8522053Z Help : [More Information](https://aka.ms/azurermwebdeployreadme)
2016-11-11T13:25:14.8522053Z ==============================================================================
2016-11-11T13:25:15.2162733Z ##[error]File not found: 'C:\a\_tasks\AzureRmWebAppDeploy_497d490f-eea7-4f2b-ab94-48d9c1acdcb1\2.1.3\azurermwebappdeployment.js'
I got same problem.
A few hours ago, with 2.1.2, it works. Now 2.1.3 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.
Logging onto the box we see that the "task.zip" file is still present in /_work/_tasks/AzureRmWebAppDeploy_49.../2.1.3/ and that not all the assets have been extracted from this file. As a workaround unzipping this zip file in the 2.1.3 folder seems to fix the issue.
Same problem here :/
we're running on a hosted agent so we cant use the work around unfortunately.
Our last successful one was at 2016-11-11T12:09:32, also with 2.1.2
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:
2016-11-11T13:02:04.7551688Z ##[error]File not found: 'C:\agent\_work\_tasks\AzureRmWebAppDeploy_497d490f-eea7-4f2b-ab94-48d9c1acdcb1\2.1.3\azurermwebappdeployment.js'
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 :
2016-11-11T14:18:29.6808379Z ##[warning]File name doesn't indicate a full path to a executable file.
2016-11-11T14:18:29.6808379Z Set workingFolder to default: D:\VsTsAgent\_work\SourceRootMapping\1d381850-f16b-4ab1-807f-11d95d0eb850\Job-035d6c31-5f2b-4967-8a59-b9d175a13011
2016-11-11T14:18:29.6848419Z ##[error]System.ComponentModel.Win32Exception (0x80004005): The directory name is invalid
2016-11-11T14:18:29.6858429Z ##[error] at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
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
@asadsahi On the build agent you should go to the _work\ _tasks\AzureRmWebAppDeploy(something)\2.1.3 directory and extract the task.zip in the 2.1.3 directory, as @jakobehn suggested. It worked for me.
@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.
[section]Starting: Deploy AzureRM App Service: XXXXXXXXXXXXXXX
module.js:341
throw err;
^
Error: Cannot find module 'vsts-task-lib/task'
at Function.Module._resolveFilename (module.js:339:15)
at Function.Module._load (module.js:290:25)
at Module.require (module.js:367:17)
at require (internal/module.js:16:19)
at Object.
at Module._compile (module.js:413:34)
at Object.Module._extensions..js (module.js:422:10)
at Module.load (module.js:357:32)
at Function.Module._load (module.js:314:12)
at Function.Module.runMain (module.js:447:10)
##[error]Exit code 1 returned from process: file name 'C:\agent\externals\node\bin\node.exe', arguments '"C:\agent_work_tasks\AzureRmWebAppDeploy_497d490f-eea7-4f2b-ab94-48d9c1acdcb1\2.1.3\azurermwebappdeployment.js"'.
##[section]Finishing: Deploy AzureRM App Service: xxxxxx
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.
Most helpful comment
Sorry for the inconvenience we fixed the issue, you should be able to use the task.