Build Artifact 和 Pipeline Artifact 任务有什么区别? [英] What is the difference between Build Artifact and Pipeline Artifact tasks?

问题描述

在 Azure DevOps 中，我们有 下载/发布 构建工件任务和下载/发布 管道工件任务.

In Azure DevOps, we have Download/Publish Build Artifact tasks and Download/Publish Pipeline Artifact tasks.

构建工件任务和管道工件任务之间有什么区别，我们什么时候会选择一个?

What is the difference between the build artifact tasks and the pipeline artifact tasks and when would we choose one over the other?

推荐答案

Azure DevOps GitHub 和微软回答:

大家好 - 我来自 Azure Artifacts 团队，我们构建了你在 Azure Pipelines 中发现的 Pipeline Artifacts 功能.

Hey everyone - I'm from the Azure Artifacts team and we built the Pipeline Artifacts feature that you've discovered in Azure Pipelines.

我将讨论关于文档的最重要的评论——我们已经关于 Azure Pipelines 中的 Artifacts 出现了一个全新的页面其中列出了我们支持的每种工件类型以及它们是什么以及指向特定文档的链接.我们认为应该回答您的大部分问题.

I'll address the most important comment around documentation - we've got a whole new page coming out around Artifacts in Azure Pipelines which lists out each artifact type that we support and what they are for along with links to specific documentation. We think that should answer most of your questions.

因为在我们发布之前仍在编辑中，我认为我会给你 30,000 英尺的管道之间的差异视图Artifacts 和 Build Artifacts 并提到 Pipeline Artifacts与通用包相关.

Because that is still being edited before we publish it I thought I would give you the 30,000 foot view on the difference between Pipeline Artifacts and Build Artifacts and also mention how Pipeline Artifacts relate to Universal Packages.

构建工件(通过发布构建工件任务发布)具有在 Azure DevOps 中使用了很长时间并且是内置工件Azure Pipelines 的存储机制.大多数构建存储今天的非包工件可能会使用此任务.任务可以将内容推送到服务器/云，但也可以将文件复制到本地文件共享.

Build Artifacts (published via the Publish Build Artifacts task) have been in Azure DevOps for a long time and are the built-in artifact storage mechanism for Azure Pipelines. Most builds that store non-package artifacts today would likely use this task. The task can push the content up to the server/cloud but can also copy the files to a local file share.

管道工件(使用发布管道工件任务发布旨在作为构建工件的替代品.他们在现在预览，还有一些我们需要做的事情达到平价.管道工件的好处是它们可以大大减少上传和下载大文件所需的时间文物.我们这样做是首先检查内容是否是正在上传存在于服务中.我们这样做不仅在每个文件级别以及子文件级别(最多 128K 块).它可以带来真正显着的性能改进.

Pipeline Artifacts (published using the Publish Pipeline Artifact task are intended as the replacement for Build Artifacts. They are in preview right now and there are a few more things we need to do to reach parity. The benefit of Pipeline Artifacts is that they can dramatically reduce the time it takes to upload and download large artifacts. We do this be first checking whether the content that is being uploaded exists in the service. We do this not just at the per-file level but also at the sub-file level (in up to 128K chunks). It can lead to really dramatic performance improvements.

通用包 - 也在预览中使用相同的存储/传输技术作为管道工件.你会使用通用包当你想创造一个生命周期独立的工件时创建它的管道.您可以下载管道工件在通过工件 UX 完成管道后 - 但如果您愿意真正独立于管道而存在的东西通用包.之间应该没有性能差异两个.

Universal Packages - also in preview use the same storage/transfer technology as Pipeline Artifacts. You would use Universal Packages when you want to create an artifact with a life time independent of the pipeline that created it. You can download Pipeline Artifacts after a pipeline has completed via the artifacts UX - but if you want something that really exists independent of pipeline you would go for Universal Packages. There should be no performance difference between the two.

希望这会有所帮助.随意提出任何更多问题，我会跟进答复.

Hopefully this helps. Feel free to ask any more questions and I'll follow-up with answers.

这篇关于Build Artifact 和 Pipeline Artifact 任务有什么区别?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！