Below is Azure error log from the Azure release pipeline.
2020-07-24T05:17:13.7712974Z ##[section]Starting: Deploy Azure App Service
2020-07-24T05:17:14.0464143Z ==============================================================================
2020-07-24T05:17:14.0465719Z Task : Azure App Service deploy
2020-07-24T05:17:14.0469391Z Description : Deploy to Azure App Service a web, mobile, or API app using Docker, Java, .NET, .NET Core, Node.js, PHP, Python, or Ruby
2020-07-24T05:17:14.0469849Z Version : 3.163.5
2020-07-24T05:17:14.0470410Z Author : Microsoft Corporation
2020-07-24T05:17:14.0470921Z Help : https://aka.ms/azureappservicetroubleshooting
2020-07-24T05:17:14.0471274Z =============================================================================
2020-07-24T05:17:16.0650643Z Got connection details for Azure App Service:'XXXXX'
2020-07-24T05:17:17.6576087Z (node:764) Warning: Use Cipheriv for counter mode of aes-256-ctr
**2020-07-24T05:17:17.6627737Z ##[error]Error: No package found with specified pattern: D:\a\r1\a\Drop<br/>Check if the package mentioned in the task is published as an artifact in the build or a previous stage and downloaded in the current job.**
2020-07-24T05:17:22.9168975Z Successfully added release annotation to the Application Insight : XXXXX
2020-07-24T05:17:24.8686063Z Successfully updated deployment History at https://XXXXX.scm.azurewebsites.net/api/deployments/231595567842919
2020-07-24T05:17:24.8933576Z ##[section]Finishing: Deploy Azure App Service
P.S. I have checked build pipeline, I can download build Artificats, but it displays below warning.
[warning]Directory 'D:\a\1\a' is empty. Nothing will be added to build artifact 'drop'.
Assuming you meant you have solved the build artifact empty issue, but the release pipeline still had issue in Azure App Service deploy task.
As the error mentioned, there is "No package found with specified pattern: D:\a\r1\a\Drop", you need to check how you define the package, try format $(System.DefaultWorkingDirectory)/**/*.zip instead of $(System.DefaultWorkingDirectory)\Drop.
As task "Publish Build Artifact" publish artifact from $(build.artifactstagingdirectory), so we need add a task "Copy files" to copy your files ** from $(system.defaultworkingdirectory) to $(build.artifactstagingdirectory) **. which copied my build to stagingdirectory.
Related
hope to get some help as I'm struggling to get a NextJS or any type of node project to successfully deploy on Azure with DevOps pipeline.
I have all the steps and configuration working on the Repo PR to then run a build and finally the triggered Release. It will pull down the zip artifact from the build, however I always get an error on the agent job for the task "Azure Web App Deploy".
In short the job appears to always run a yarn install command vs. the Startup Command setting.
My setup is as follows:
Task Settings
Azure Web App Deploy task error
Tried with different Startup commands, which none display in the task.
I added the following in the "Application and Configuration Settings" section of the task:
-SCM_DO_BUILD_DURING_DEPLOYMENT FALSE
-build-remote true
When the release pipeline run end up with this error
RangeError [ERR_INVALID_OPT_VALUE]: The value "4294967295" is invalid for option "size".
I don't know what means this error
task failed
Log of the task failed when release run
Same issue for me using Web Deploy to a nodejs app service.
Web Deploy worked at first, until we added some packages in our package.json (e.g. "#fortawesome/free-brands-svg-icons")
Then our release pipeline suddenly outputs "64-bit = +" in the deployment log.
If we remove the packages, the "64-bit = +" is gone, and our Web Deploy works again.
Image of log from Release pipeline
Not sure how to resolve it, but in our case we used Zip Deploy instead like #Ari Gunawan recommended.
I had the same issue when trying to deploy a node app to Azure App Service from release pipeline. Not sure what the error means as there are no further details about it but I resolved it by using "Zip Deploy" deployment method and "Continue on error"
Goal
I'm trying to install IIS on remote server using azure devops. I have done this on other vm servers without issue.
Problem
When running this stage the Agent Errors with very little details
Agent Errors when installing IIS
Error
2020-08-11T19:06:19.1822182Z ##[section]Starting: IIS Web App Manage
2020-08-11T19:06:19.1984662Z ==============================================================================
2020-08-11T19:06:19.1985052Z Task : IIS web app manage
2020-08-11T19:06:19.1985379Z Description : Create or update websites, web apps, virtual directories, or application pools
2020-08-11T19:06:19.1985671Z Version : 0.5.15
2020-08-11T19:06:19.1985908Z Author : Microsoft Corporation
2020-08-11T19:06:19.1986227Z Help : https://learn.microsoft.com/azure/devops/pipelines/tasks/deploy/iis-web-app-management-on-machine-group
2020-08-11T19:06:19.1986625Z ==============================================================================
2020-08-11T19:06:21.2180244Z Installing IIS. This may take few minutes.
2020-08-11T19:06:46.1602426Z ##[error]The request to add or remove features on the specified server failed.
Installation of one or more roles, role services, or features failed.
The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077. Error: 0x800f081f
2020-08-11T19:06:46.1908491Z ##[section]Finishing: IIS Web App Manage
Stage Settings
steps:
- task: IISWebAppManagementOnMachineGroup#0
displayName: 'Manage IISWebsite'
inputs:
EnableIIS: true
WebsiteName: 'Default Web Site'
AddBinding: true
Bindings: '{"bindings":[{"protocol":"http","ipAddress":"All Unassigned","port":"80","hostname":"","sslThumbprint":"","sniFlag":false}]}'
CreateOrUpdateAppPoolForWebsite: true
AppPoolNameForWebsite: default
I solved this by stop trying to use the prebuilt IIS web app manage tool and ended up just installing iis via power shell command
Install-WindowsFeature -name Web-Server -IncludeManagementTools
I am unable to publish new packages to (or restore packages from) my own NuGet Feed in Azure DevOps . It started a few days ago and, since I have created a brand new feed (out of curiosity). Still, it fails with the same error:
Failed to find api location for area: nuget id:
9D3A4E8E-2F8F-4AE1-ABC2-B461A51CB3B3
2019-05-27T22:09:46.8693807Z ##[section]Starting: dotnet push (Common)
2019-05-27T22:09:46.8802338Z ==============================================================================
2019-05-27T22:09:46.8802573Z Task : .NET Core
2019-05-27T22:09:46.8802607Z Description : Build, test, package, or publish a dotnet application, or run a custom dotnet command. For package commands, supports NuGet.org and authenticated feeds like Package Management and MyGet.
2019-05-27T22:09:46.8802660Z Version : 2.151.1
2019-05-27T22:09:46.8802692Z Author : Microsoft Corporation
2019-05-27T22:09:46.8802724Z Help : [More Information](https://go.microsoft.com/fwlink/?linkid=832194)
2019-05-27T22:09:46.8802931Z ==============================================================================
2019-05-27T22:09:47.4837790Z [command]C:\windows\system32\chcp.com 65001
2019-05-27T22:09:47.4924880Z Active code page: 65001
2019-05-27T22:09:47.4964761Z SYSTEMVSSCONNECTION exists true
2019-05-27T22:09:47.5770818Z SYSTEMVSSCONNECTION exists true
2019-05-27T22:09:50.7225430Z SYSTEMVSSCONNECTION exists true
2019-05-27T22:09:50.7673768Z ##[warning]Can\'t find loc string for key: Warning_SessionCreationFailed
2019-05-27T22:09:50.7683040Z ##[warning]Warning_SessionCreationFailed {}
2019-05-27T22:09:52.3193091Z ##[error]Error: Error: Failed to find api location for area: nuget id: 9D3A4E8E-2F8F-4AE1-ABC2-B461A51CB3B3
2019-05-27T22:09:52.3194182Z ##[error]Packages failed to publish
2019-05-27T22:09:52.3294148Z ##[section]Finishing: dotnet push (Common)
How can I fix this error?
Unable to restore NuGet Package: “Failed to find api location for area: nuget id: 9D3A4E8E”
The reason for the above error is a wrong specification of the URL of the service to use.
So, to resolve this issue, please try to double check if the source of nuget feed is correct.
If the source of nuget feed is correct and this issue is also occurred on the other nuget feed(which is worked before.), you can try to delete the brand new feed, then check if this issue is resolved.
If this issue only occurred on the brand new feed, please try to check if your feed configured correctly and check if the agent has any proxy setting.
Check the ticket VSTS - Cannot Push Nuget Package to VSTS Package Feed from Private Agent Behind Web Proxy
Hope this helps.
I have a .NET Core repo in VSTS. I'm trying to create a Build pipeline that builds a Docker image and adds it to my Azure Container Registry. My Build pipeline has a Docker task. This task has the "Build an image" action selected. This action relies on my Dockerfile, which looks like this:
FROM microsoft/dotnet:2.1.2-runtime-nanoserver-1803
# Install .NET Core
ENV DOTNET_VERSION 2.1.2
When my Build pipeline runs, I get an error that says:
failed to register layer: re-exec error: exit status 1: output: ProcessUtilityVMImage \\?\C:\ProgramData\docker\windowsfilter\82aba535faccd8bf0e5ce3c122247672fa671214000a12c5481972212c5e2ca0\UtilityVM: The system cannot find the path specified.
##[error]C:\Program Files\Docker\docker.exe failed with return code: 1
Why am I getting this error? How do I fix it?
It should be the same issue with this one : https://github.com/Microsoft/vsts-tasks/issues/6510
Seems it still have some issues with nanoserver-1803
Just try to setup and host a custom agent on Azure VM, then check it again.
https://github.com/Microsoft/vsts-tasks/issues/6510#issuecomment-370152300
I found maybe an explication about this error: VSTS agents seem not
support nanoserver-1709 actually. Maybe this will change with the next
version 1803.
See details here: Microsoft/vsts-agent#1393
When I setup and host a custom agent on a machine on Azure, it's
working. So it's not a bug with this task. I close this issue. Thanks!