删除构建记录时是否应该删除与构建记录关联的工件? [英] Should artifacts associated with a build record be deleted when the build record is deleted?

查看:16
本文介绍了删除构建记录时是否应该删除与构建记录关联的工件?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在使用带有本地构建代理的新 VSO 可编写脚本的构建系统.

I am using the new VSO scriptable build system with an on premise build agent.

构建将以下资产发布到内部文件共享.

The build publishes the following assets to an internal file share.

  1. 安装
  2. 我们内部符号存储的符号.

当手动或基于保留策略删除构建时,相关资产不会被删除.

When a build is deleted either manually or based on retention policy the associated assets are not deleted.

当关联的构建记录被删除时,我应该期望资产被删除吗?

Should I expect that assets are deleted when the associated build record is deleted?

推荐答案

在 2015 RTM 和当前在 VSO 中,删除构建时删除服务器删除,但不会删除删除到 UNC 共享.

In 2015 RTM and currently in VSO, server drops are deleted when a build is deleted but drops to UNC shares are not.

我们正在处理积压工作来解决这个问题.

We have work on our backlog to address this.

在 2015 QU2 中,此功能已启用.此外,如果您在最近的 sprint 中针对 VSTS 使用本地代理,则它可以工作.它将作业排队以删除具有与构建构建相同的要求的共享.这可能会出现在作为写入 UNC 共享的同一帐户运行的代理上.它使用代理运行的帐户尝试删除共享(尽力而为)

In 2015 QU2, this is enabled. Also if you on-prem agents against VSTS in recent sprints it works. It queues the job to delete the share with the same demands that the build was built with. This likely lands on an agent running as the same account that wrote to the UNC share. It uses the account the agent runs as to attempt to delete the share (best effort)

这篇关于删除构建记录时是否应该删除与构建记录关联的工件?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆