Azure Pipelines：PublishBuildArtifacts 和 PublishPipelineArtifact 任务之间的区别？
Azure Pipelines : differences between PublishBuildArtifacts and PublishPipelineArtifact tasks?
我注意到 PublishPipelineArtifact 任务的存在，但我不清楚是否与旧的 PublishBuildArtifacts[=14 有任何功能差异=] 任务?
构建工件：构建工件是您希望构建生成的文件。构建工件几乎可以是您的团队测试或部署您的应用程序所需的任何东西。例如，您有 .dll 和 .exe 可执行文件以及 .NET 或 C++ Windows 应用程序的 .PDB 符号文件。
管道工件：您可以使用管道工件来帮助存储构建输出并在管道中的作业之间移动中间文件。管道工件与创建它们的管道相关联。您可以在管道中使用它们并从构建中下载它们，只要保留构建。管道工件是新一代的构建工件。他们利用现有服务来显着减少在管道中存储输出所需的时间。仅适用于 Azure DevOps 服务。
GitHub 上有一个关于它的问题，Microsoft 回答：
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.
Pipeline Artifacts (published using the Publish Pipeline Artifact
task are intended as the replacement for Build Artifacts). 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.
另外，这里有一个同样问题的可以参考
我注意到 PublishPipelineArtifact 任务的存在，但我不清楚是否与旧的 PublishBuildArtifacts[=14 有任何功能差异=] 任务?
构建工件：构建工件是您希望构建生成的文件。构建工件几乎可以是您的团队测试或部署您的应用程序所需的任何东西。例如，您有 .dll 和 .exe 可执行文件以及 .NET 或 C++ Windows 应用程序的 .PDB 符号文件。
管道工件：您可以使用管道工件来帮助存储构建输出并在管道中的作业之间移动中间文件。管道工件与创建它们的管道相关联。您可以在管道中使用它们并从构建中下载它们，只要保留构建。管道工件是新一代的构建工件。他们利用现有服务来显着减少在管道中存储输出所需的时间。仅适用于 Azure DevOps 服务。
GitHub 上有一个关于它的问题，Microsoft 回答：
Build Artifacts (published via the
Publish Build Artifactstask) 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.Pipeline Artifacts (published using the
Publish Pipeline Artifacttask are intended as the replacement for Build Artifacts). 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.
另外，这里有一个