希望有人也看到了。我们最后一次成功建造是在2019年12月6日。新的部署尝试在部署步骤失败(与生成和发布管道中的问题相同)。
错误报告如下:
Got service connection details for Azure App Service:'OUR SITE'
Package deployment using ZIP Deploy initiated.
## [error]Failed to deploy web package to App Service.
## [error]Error: Error: Failed to deploy web package to App Service. Conflict (CODE: 409)
## [warning]Error: Failed to update deployment history. Error: Bad Request (CODE: 400)
App Service Application URL: OUR SITE
这是我们的部署 YAML
,抱歉,我已经做了好几天了:(
# Node.js Express Web App to Linux on Azure
# Build a Node.js Express app and deploy it to Azure as a Linux web app.
# Add steps that analyze code, save build artifacts, deploy, and more:
# https://docs.microsoft.com/azure/devops/pipelines/languages/javascript
trigger:
- master
variables:
# Azure Resource Manager connection created during pipeline creation
azureSubscription: '[OUR SUB ID]'
# Web app name
webAppName: 'website-to-deploy'
# Environment name
environmentName: 'web-to-deploy'
# Agent VM image name
vmImageName: 'ubuntu-latest'
stages:
- stage: Build
displayName: Build stage
jobs:
- job: Build
displayName: Build
pool:
vmImage: $(vmImageName)
steps:
- task: NodeTool@0
inputs:
versionSpec: '10.x'
displayName: 'Install Node.js'
- script: |
npm install
npm run build --if-present
npm run test --if-present
displayName: 'npm install, build and test'
- task: ArchiveFiles@2
displayName: 'Archive files'
inputs:
rootFolderOrFile: '$(System.DefaultWorkingDirectory)'
includeRootFolder: false
archiveType: zip
archiveFile: $(Build.ArtifactStagingDirectory)/$(Build.BuildId).zip
replaceExistingArchive: true
- upload: $(Build.ArtifactStagingDirectory)/$(Build.BuildId).zip
artifact: drop
- task: AzureRmWebAppDeployment@4
inputs:
ConnectionType: 'AzureRM'
azureSubscription: 'OUR SUBSCRIPTION'
appType: 'webAppLinux'
WebAppName: 'site-to-deploy'
packageForLinux: $(Build.ArtifactStagingDirectory)/$(Build.BuildId).zip
RuntimeStack: 'NODE|12-lts'
StartupCommand: 'npm start'
AppSettings: 'WE DO HAVE SOME SETTINGS'
请注意:我已尝试添加 WEBSITE_WEBDEPLOY_USE_SCM = true
对于配置来说,这没有帮助。
以上版本没有任何更改 YAML
这是成功的工作和饲料到释放管道
谢谢你的帮助。
更新:您可以添加ms dev ops引发的问题 system.debug: true
在变量部分中,可以获得更详细的日志记录。
这让我看到 AppService
返回 409
代码,因为它认为部署已经在进行中。如果我得到一个决议,我会编辑这篇文章。
以下是调试信息:
## [debug]Encountered a retriable status code: 409. Message: 'Conflict'.
## [debug][POST]https://$web040-glndev-com:***@web040-glndev-com.scm.azurewebsites.net/api/zipdeploy?isAsync=true&deployer=VSTS_ZIP_DEPLOY
## [debug]Could not parse response: {}
## [debug]Response: undefined
## [debug]Encountered a retriable status code: 409. Message: 'Conflict'.
## [debug][POST]https://$web040-glndev-com:***@web040-glndev-com.scm.azurewebsites.net/api/zipdeploy?isAsync=true&deployer=VSTS_ZIP_DEPLOY
## [debug]Could not parse response: {}
## [debug]Response: undefined
## [debug]ZIP Deploy response: {"statusCode":409,"statusMessage":"Conflict","headers":{"transfer-encoding":"chunked","content-type":"text/plain; charset=utf-8","server":"Kestrel","date":"Wed, 15 Jan 2020 17:40:47 GMT","connection":"close"},"body":"There is a deployment currently in progress. Please try again when it completes."}
## [error]Failed to deploy web package to App Service.
## [debug]Processed: ##vso[task.issue type=error;]Failed to deploy web package to App Service.
## [debug]task result: Failed
## [error]Error: Error: Failed to deploy web package to App Service. Conflict (CODE: 409)
## [debug]Processed: ##vso[task.issue type=error;]Error: Error: Failed to deploy web package to App Service. Conflict (CODE: 409)
## [debug]Processed: ##vso[task.complete result=Failed;]Error: Error: Failed to deploy web package to App Service. Conflict (CODE: 409)
## [debug][POST]https://management.azure.com/subscriptions/7a7aad03-79b0-4118-8dd1-8ebd63716c6a/resourceGroups/appsvc_linux_centralus/providers/Microsoft.Web/sites/web040-glndev-com/config/appsettings/list?api-version=2016-08-01
## [debug]Correlation ID from ARM api call response : e4ebaf0f-7ccf-4b7b-ba4d-b70b8fd13bea
## [debug]Application Insights is not configured for the App Service. Skipping adding release annotation.
票证在这里:409无法部署web包
4条答案
按热度按时间pw136qt21#
我也有同样的错误,问题是webapp的大小。我尝试将超过1gb的Web应用部署到应用服务计划层为1gb的azure Web应用。
eimct9ow2#
重新启动应用程序服务解决了我的问题。
我的应用服务计划已经是付费订阅,容量没有问题。我刚刚重启了应用程序服务,一切正常。
kxe2p93d3#
目前(2020年7月/8月)的问题实际上是microsoft对支持某些地区应用程序服务的虚拟机的更新,如github问题中所述:https://github.com/projectkudu/kudu/issues/3042
解决办法(在此答复中列出:https://github.com/projectkudu/kudu/issues/3042#issuecomment-665997217)似乎有帮助。任何一个
通过scm门户重新启动kudu(通过process explorer选项卡终止w3wp进程)
重新启动应用程序服务(导致停机)
向上和向下扩展您的服务(尽管有些人报告他们必须在这两者之间进行部署)
gv8xihay4#
因此,在与微软支持人员进行了大量讨论之后,这是一张罚单
据透露,真正的问题是,我的应用程序服务计划是在容量。在开发过程中,我们使用的是免费服务,而且有一定的局限性。我们已经达到了这个极限,这条信息只是一条红鲱鱼,根本不是真正的问题。
不管怎样,我升级到了付费订阅的第一层,现在一切都正常了。