Azure devops 发生一个或多个错误时如何调试Azure DevOps任务PublishPipelineArtifact
我正试图建立一个管道,将1。生成一个文件(jar)和2。使用第一个作业的输出构建Docker映像。按照这种方法,我理解不能使用第一阶段来构建Docker映像,因为我正在构建的Maven容器中没有Docker引擎。因此,我设置了第二个作业,但这意味着构建上下文不共享。因此,我尝试使用Azure devops 发生一个或多个错误时如何调试Azure DevOps任务PublishPipelineArtifact,azure-devops,Azure Devops,我正试图建立一个管道,将1。生成一个文件(jar)和2。使用第一个作业的输出构建Docker映像。按照这种方法,我理解不能使用第一阶段来构建Docker映像,因为我正在构建的Maven容器中没有Docker引擎。因此,我设置了第二个作业,但这意味着构建上下文不共享。因此,我尝试使用PublishPipelineArtifact任务(publish步骤)然后使用DownloadPipelineArtifact(Download步骤)进行检索,但出现以下故障(System.Debug为true)。H
PublishPipelineArtifact
任务(publish
步骤)然后使用DownloadPipelineArtifact
(Download
步骤)进行检索,但出现以下故障(System.Debug
为true
)。Have verified proxy未阻塞,但不知道如何继续调试,因为任务似乎超时
##[debug]Evaluating condition for step: 'PublishPipelineArtifact'
##[debug]Evaluating: SucceededNode()
##[debug]Evaluating SucceededNode:
##[debug]=> True
##[debug]Result: True
Starting: PublishPipelineArtifact
==============================================================================
Task : Publish pipeline artifact
Description : Publish (upload) a file or directory as a named artifact for the current run
Version : 1.2.0
Author : Microsoft Corporation
Help : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/publish-pipeline-artifact
==============================================================================
Artifact name input: sampleTextFile
Uploading pipeline artifact from /home/mt/vsts/_work/45/s/publish-build-artifact/test.txt for build #11684
##[debug]Dedup parallelism: 192
##[error]One or more errors occurred. (A task was canceled.)
##[debug]Processed: ##vso[task.logissue type=error;]One or more errors occurred. (A task was canceled.)
##[debug]Processed: ##vso[task.complete result=Failed;]
##[debug] at System.Threading.Tasks.Task`1.GetResultCore(Boolean waitCompletionNotification)
at Microsoft.VisualStudio.Services.BlobStore.Common.Telemetry.BlobStoreApplicationInsightsTelemetrySender..ctor(IAppTraceSource tracer, Uri baseAddress)
at Agent.Plugins.PipelineArtifact.DedupManifestArtifactClientFactory.CreateDedupManifestClient(AgentTaskPluginExecutionContext context, VssConnection connection, CancellationToken cancellationToken, BlobStoreClientTelemetry& telemetry)
at Agent.Plugins.PipelineArtifact.PipelineArtifactServer.UploadAsync(AgentTaskPluginExecutionContext context, Guid projectId, Int32 pipelineId, String name, String source, CancellationToken cancellationToken)
at Agent.Plugins.PipelineArtifact.PublishPipelineArtifactTaskV1.ProcessCommandInternalAsync(AgentTaskPluginExecutionContext context, CancellationToken token)
at Agent.PluginHost.Program.Main(String[] args)
Finishing: PublishPipelineArtifact
我使用的最小管道配置文件(剥离了Java构建和Docker构建步骤):
应该使用
PublishBuildArtifacts
而不是PublishPipelineArtifact
.很高兴知道。你能解释一下原因吗?嗨,朋友,谢谢你在这里分享这个解决方案。请将您的回复标记为答案,这将帮助其他社区成员更容易搜索此有用信息,只是提醒一下:)这里有什么问题?为什么我不能使用PublishPipelineArtifact?
trigger:
- master
stages:
- stage: Build
jobs:
- job: FirstJob
pool:
name: my-pool
demands:
- docker
container:
image: 'maven:latest'
steps:
- publish: $(System.DefaultWorkingDirectory)/publish-build-artifact/test.txt
artifact: sampleTextFile
- job: SecondJob
dependsOn: FirstJob
condition: succeeded()
pool:
name: my-pool
demands:
- docker
steps:
- download: current
artifact: sampleTextFile