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

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

问题描述

我正在将新的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天全站免登陆