Kudu 尝试从旧的 Azure Branch 分支进行 Zip Deploy
Kudu trying to Zip Deploy from old Azure Branch branch
我制作了一个 Azure DevOps YAML 管道，它成功部署到我们的测试环境中；我已经复制了该管道更改了我们的暂存环境的应用程序名称并且管道失败并发出此错误：
##[error]Failed to deploy web package to App Service.
##[error]To debug further please check Kudu stack trace URL : https://$nsclassroom-vxh3zokbtum5i:***@nsclassroom-vxh3zokbtum5i.scm.azurewebsites.net/api/vfs/LogFiles/kudu/trace
##[error]Error: Package deployment using ZIP Deploy failed. Refer logs for more details.
这是该管道的 YAML 文件：
variables:
System.Debug: false
azureSubscription: 'WebsitePipelineJC'
RG: 'MY VALUE'
Location: UK South
containername: 'private'
appconnectionname: 'WebsitePipelineJC'
stages:
- stage: Deploy
jobs:
- job: job1
displayName: Create And Publish Artifact
pool:
vmImage: vs2017-win2016
steps:
- task: UseDotNet@2
displayName: Use .Net Core 3.1.x SDK
inputs:
packageType: 'sdk'
version: '3.1.x'
- task: DotNetCoreCLI@2
displayName: dotnet restore
inputs:
command: restore
projects: 'Website.csproj'
- task: Npm@1
displayName: 'npm install'
inputs:
workingDir: ClientApp
verbose: false
- task: Npm@1
displayName: 'npm run build'
inputs:
command: 'custom'
workingDir: ClientApp
customCommand: 'build'
- task: DotNetCoreCLI@2
displayName: dotnet build
inputs:
projects: 'Website.csproj'
arguments: '--configuration Release'
- task: DotNetCoreCLI@2
displayName: dotnet Test
inputs:
command: test
projects: 'UnitTests/UnitTests.csproj'
arguments: '--configuration Release'
- task: DotNetCoreCLI@2
displayName: dotnet publish
inputs:
command: publish
projects: 'Website.csproj'
arguments: '--configuration Release --output
$(Build.ArtifactStagingDirectory)'
zipAfterPublish: true
modifyOutputPath: false
- task: PublishPipelineArtifact@1
displayName: Publish Pipeline Artifact
inputs:
targetPath: '$(Build.ArtifactStagingDirectory)'
artifact: 'Website'
publishLocation: 'pipeline'
- job: job2
displayName: Create Web App
dependsOn: job1
steps:
# Download Artifact File
- download: none
- task: DownloadPipelineArtifact@2
displayName: 'Download Build Artifacts'
inputs:
patterns: '**/*.zip'
path: '$(Build.ArtifactStagingDirectory)'
# deploy to Azure Web App
- task: AzureWebApp@1
displayName: 'Azure Web App Deploy: nsclassroom-dgyn27h2dfoyo'
inputs:
package: $(Build.ArtifactStagingDirectory)/**/*.zip
azureSubscription: $(azureSubscription)
ConnectedServiceName: $(appconnectionname)
appName: 'nsclassroom-dgyn27h2dfoyo'
ResourceGroupName: $(RG)
接着，我进入了 Kudu 日志。我发现 Kudu 正在尝试部署到我们不再拥有的旧分支，即使 Pipeline YAML 代码位于完全不同的分支中，并且 YAML 代码指定了我要部署到的分支。
这是 KUDU 输出的日志。旧分支叫staging-hp，新分支就叫staging。
<step title="BackgroundTrace" date="2021-05-26T14:54:09.702" instance="bdff23" url="/api/zipdeploy" method="POST">
<step title="LockFile 'C:\home\site\locks\deployments.lock' acquired" date="2021-05-26T14:54:09.718"/>
<!-- duration: 16ms -->
<step title="Creating temporary deployment" date="2021-05-26T14:54:09.733"/>
<!-- duration: 62ms -->
<step title="Performing fetch based deployment" date="2021-05-26T14:54:09.811">
<step title="Before sending BuildRequestReceived status to /api/updatedeploystatus" date="2021-05-26T14:54:09.936"/>
<!-- duration: 0ms -->
</step>
<!-- duration: 219ms -->
<step title="LockFile 'C:\home\site\locks\deployments.lock' released" date="2021-05-26T14:54:10.061"/>
<!-- duration: 16ms -->
<step title="Error occurred" date="2021-05-26T14:54:10.077" type="error" text="One or more errors occurred." stackTrace=" at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions) at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken) at Kudu.Core.Deployment.FetchDeploymentManager.<>c__DisplayClass11_1.<PerformBackgroundDeployment>b__3() in C:\Kudu Files\Private\src\master\Kudu.Core\Deployment\FetchDeploymentManager.cs:line 396 at Kudu.Contracts.Infrastructure.LockExtensions.TryLockOperation(IOperationLock lockObj, Action operation, String operationName, TimeSpan timeout) in C:\Kudu Files\Private\src\master\Kudu.Contracts\Infrastructure\LockExtensions.cs:line 34 at Kudu.Contracts.Infrastructure.LockExtensions.LockOperation(IOperationLock lockObj, Action operation, String operationName, TimeSpan timeout) in C:\Kudu Files\Private\src\master\Kudu.Contracts\Infrastructure\LockExtensions.cs:line 46 at Kudu.Core.Deployment.FetchDeploymentManager.<>c__DisplayClass11_0.<PerformBackgroundDeployment>b__1() in C:\Kudu Files\Private\src\master\Kudu.Core\Deployment\FetchDeploymentManager.cs:line 380" innerText="ChangeSetId(staging-hp) does not match 479f5474d10445218660a74f0664e206, 'master' or 'HEAD'" innerStackTrace=" at Kudu.Core.SourceControl.NullRepository.GetChangeSet(String id) in C:\Kudu Files\Private\src\master\Kudu.Core\SourceControl\NullRepository.cs:line 81 at Kudu.Core.Deployment.FetchDeploymentManager.<PerformDeployment>d__9.MoveNext() in C:\Kudu Files\Private\src\master\Kudu.Core\Deployment\FetchDeploymentManager.cs:line 224 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at Kudu.Core.Deployment.FetchDeploymentManager.<PerformDeployment>d__9.MoveNext() in C:\Kudu Files\Private\src\master\Kudu.Core\Deployment\FetchDeploymentManager.cs:line 292"/>
<!-- duration: 16ms -->
</step>
<!-- duration: 406ms -->
我想通了，wwwroot/site/deployments/ 中有一个 settings.xml 文件，上面有旧分支的详细信息。如果你删除 settings.xml 它会放弃那个分支。您可能无法删除该文件，因为它设置为只读权限，您需要做的是进入您的网络应用程序的配置设置并将 WEBSITE_RUN_FROM_PACKAGE 值更改为 0，保存并刷新网络应用程序，然后您将能够删除该文件。然后你可以重新运行管道，直到你心满意足为止。 :)
我制作了一个 Azure DevOps YAML 管道，它成功部署到我们的测试环境中；我已经复制了该管道更改了我们的暂存环境的应用程序名称并且管道失败并发出此错误：
##[error]Failed to deploy web package to App Service.
##[error]To debug further please check Kudu stack trace URL : https://$nsclassroom-vxh3zokbtum5i:***@nsclassroom-vxh3zokbtum5i.scm.azurewebsites.net/api/vfs/LogFiles/kudu/trace
##[error]Error: Package deployment using ZIP Deploy failed. Refer logs for more details.
这是该管道的 YAML 文件：
variables:
System.Debug: false
azureSubscription: 'WebsitePipelineJC'
RG: 'MY VALUE'
Location: UK South
containername: 'private'
appconnectionname: 'WebsitePipelineJC'
stages:
- stage: Deploy
jobs:
- job: job1
displayName: Create And Publish Artifact
pool:
vmImage: vs2017-win2016
steps:
- task: UseDotNet@2
displayName: Use .Net Core 3.1.x SDK
inputs:
packageType: 'sdk'
version: '3.1.x'
- task: DotNetCoreCLI@2
displayName: dotnet restore
inputs:
command: restore
projects: 'Website.csproj'
- task: Npm@1
displayName: 'npm install'
inputs:
workingDir: ClientApp
verbose: false
- task: Npm@1
displayName: 'npm run build'
inputs:
command: 'custom'
workingDir: ClientApp
customCommand: 'build'
- task: DotNetCoreCLI@2
displayName: dotnet build
inputs:
projects: 'Website.csproj'
arguments: '--configuration Release'
- task: DotNetCoreCLI@2
displayName: dotnet Test
inputs:
command: test
projects: 'UnitTests/UnitTests.csproj'
arguments: '--configuration Release'
- task: DotNetCoreCLI@2
displayName: dotnet publish
inputs:
command: publish
projects: 'Website.csproj'
arguments: '--configuration Release --output
$(Build.ArtifactStagingDirectory)'
zipAfterPublish: true
modifyOutputPath: false
- task: PublishPipelineArtifact@1
displayName: Publish Pipeline Artifact
inputs:
targetPath: '$(Build.ArtifactStagingDirectory)'
artifact: 'Website'
publishLocation: 'pipeline'
- job: job2
displayName: Create Web App
dependsOn: job1
steps:
# Download Artifact File
- download: none
- task: DownloadPipelineArtifact@2
displayName: 'Download Build Artifacts'
inputs:
patterns: '**/*.zip'
path: '$(Build.ArtifactStagingDirectory)'
# deploy to Azure Web App
- task: AzureWebApp@1
displayName: 'Azure Web App Deploy: nsclassroom-dgyn27h2dfoyo'
inputs:
package: $(Build.ArtifactStagingDirectory)/**/*.zip
azureSubscription: $(azureSubscription)
ConnectedServiceName: $(appconnectionname)
appName: 'nsclassroom-dgyn27h2dfoyo'
ResourceGroupName: $(RG)
接着，我进入了 Kudu 日志。我发现 Kudu 正在尝试部署到我们不再拥有的旧分支，即使 Pipeline YAML 代码位于完全不同的分支中，并且 YAML 代码指定了我要部署到的分支。
这是 KUDU 输出的日志。旧分支叫staging-hp，新分支就叫staging。
<step title="BackgroundTrace" date="2021-05-26T14:54:09.702" instance="bdff23" url="/api/zipdeploy" method="POST">
<step title="LockFile 'C:\home\site\locks\deployments.lock' acquired" date="2021-05-26T14:54:09.718"/>
<!-- duration: 16ms -->
<step title="Creating temporary deployment" date="2021-05-26T14:54:09.733"/>
<!-- duration: 62ms -->
<step title="Performing fetch based deployment" date="2021-05-26T14:54:09.811">
<step title="Before sending BuildRequestReceived status to /api/updatedeploystatus" date="2021-05-26T14:54:09.936"/>
<!-- duration: 0ms -->
</step>
<!-- duration: 219ms -->
<step title="LockFile 'C:\home\site\locks\deployments.lock' released" date="2021-05-26T14:54:10.061"/>
<!-- duration: 16ms -->
<step title="Error occurred" date="2021-05-26T14:54:10.077" type="error" text="One or more errors occurred." stackTrace=" at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions) at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken) at Kudu.Core.Deployment.FetchDeploymentManager.<>c__DisplayClass11_1.<PerformBackgroundDeployment>b__3() in C:\Kudu Files\Private\src\master\Kudu.Core\Deployment\FetchDeploymentManager.cs:line 396 at Kudu.Contracts.Infrastructure.LockExtensions.TryLockOperation(IOperationLock lockObj, Action operation, String operationName, TimeSpan timeout) in C:\Kudu Files\Private\src\master\Kudu.Contracts\Infrastructure\LockExtensions.cs:line 34 at Kudu.Contracts.Infrastructure.LockExtensions.LockOperation(IOperationLock lockObj, Action operation, String operationName, TimeSpan timeout) in C:\Kudu Files\Private\src\master\Kudu.Contracts\Infrastructure\LockExtensions.cs:line 46 at Kudu.Core.Deployment.FetchDeploymentManager.<>c__DisplayClass11_0.<PerformBackgroundDeployment>b__1() in C:\Kudu Files\Private\src\master\Kudu.Core\Deployment\FetchDeploymentManager.cs:line 380" innerText="ChangeSetId(staging-hp) does not match 479f5474d10445218660a74f0664e206, 'master' or 'HEAD'" innerStackTrace=" at Kudu.Core.SourceControl.NullRepository.GetChangeSet(String id) in C:\Kudu Files\Private\src\master\Kudu.Core\SourceControl\NullRepository.cs:line 81 at Kudu.Core.Deployment.FetchDeploymentManager.<PerformDeployment>d__9.MoveNext() in C:\Kudu Files\Private\src\master\Kudu.Core\Deployment\FetchDeploymentManager.cs:line 224 --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at Kudu.Core.Deployment.FetchDeploymentManager.<PerformDeployment>d__9.MoveNext() in C:\Kudu Files\Private\src\master\Kudu.Core\Deployment\FetchDeploymentManager.cs:line 292"/>
<!-- duration: 16ms -->
</step>
<!-- duration: 406ms -->
我想通了，wwwroot/site/deployments/ 中有一个 settings.xml 文件，上面有旧分支的详细信息。如果你删除 settings.xml 它会放弃那个分支。您可能无法删除该文件，因为它设置为只读权限，您需要做的是进入您的网络应用程序的配置设置并将 WEBSITE_RUN_FROM_PACKAGE 值更改为 0，保存并刷新网络应用程序，然后您将能够删除该文件。然后你可以重新运行管道，直到你心满意足为止。 :)