在源代码控制下创建构建
我正在努力克服我的基本结构来管理采用施舍实践。
首先,我已经完成了源文件夹结构的构建,在我的主分支下,我将文件夹作为构建。我打算将我的构建(ci、nightly、manual)存储在每个分支下。然而,当我创建新的构建定义时,我坚持使用一个字段。
工作区定义下的构建代理文件夹我应该保留它,因为它是
$SourceDir
我的源代码管理和构建服务器驻留在同一台计算机上。拖放文件夹与我的源代码管理中的构建文件夹不同,对吗?我的意思是我应该将新构建保留在源代码管理下还是 ci 服务器将自行处理它?</p>
谢谢。
I am trying to get over with my base structure to manage adopting alm practices.
First I have done structuring for my source folder structure where under my main branch I did put folder as builds. I was intending to store my builds (ci, nigthly, manual) be stored under each branch. However while I was creating a new build definition I stuck with a field.
Build agent folder under workspace definition should I leave it as it is
$SourceDir
my source control and build server are reside on same machine.Drop folder is not the same this as builds folder in my source control, right? I mean should I keep the new builds under source control or ci server will handle it itself?
Thanks.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
![扫码二维码加入Web技术交流群](/public/img/jiaqun_03.jpg)
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
将构建输出存储在版本控制中没有任何好处,但如果您的流程要求这样做,则没有什么可以阻止您这样做。您需要自定义构建过程模板来实现这一点,作为自动构建的一部分。开箱即用的每个构建都会创建源标签(可针对多种工作项类型进行访问),假设一切设置正确,您可以从构建服务器上的放置位置提取此构建的副本。
构建服务器将拥有自己的工作区定义,其中
$SourceDir
将映射到将从版本控制中提取源代码的顶级目录。 Drop 文件夹是放置最终构建输出的位置。它可以是运行构建的帐户可访问的任何本地或 UNC 文件共享。放置文件夹与您的或构建服务器本地工作区文件夹无关,因此即使您将其设置为放置文件夹,它也不会添加到版本控制中。请记住,您的本地工作区仅提供对服务器上版本控制结构的物理结构的抽象级别。简单地在本地将它们一对一映射无论如何都不会导致添加到本地的工件自动添加到服务器。
希望这是有道理的。
There's no benefit to storing your build output in version control but if your process dictates this there's nothing stopping you from doing it. You'd need to customize the build process template to achieve this as part of the automated build. Out of the box each build will create a label of the source (accessible against several workitem types) and assuming everything is setup correctly you can pull a copy of this build from the drop location on the build server.
The build server will have it's own workspace definition for which
$SourceDir
will map to the top level directory where the source will be pulled from version control. The Drop folder is where the final build output will be placed. It can be any local or UNC file share accessible to the account under which the builds are running.Drop folder isn't related to yours or the build servers local workspace folder so even if you set this as the drop folder it won't get added to version control. Remember that your local workspace just provides a level of abstraction over the physical structure of your version control structure on the server. Simply mapping them one to one locally won't in anyway cause artifacts added to the local to be automatically added to the server.
Hope that makes sense.