TeamCity - 自动化在哪里 [英] TeamCity - Where is the automation

问题描述

我们安装TeamCity和TFS，他们工作正常。我的问题是这两个应该如何使我们的工作流程有效？一旦我对我的dev机器上的代码进行更改，我必须去TeamCity UI来运行构建和测试吗？这里的自动化在哪里..我手动做它反正...我错过了一个重要的一块在这里？我可以在我的dev机器上运行构建和单元测试。所有开发人员进行更改，需要转到TeamCity UI来构建更新的代码？我希望TeamCity能够自动检测TFS的更改，并立即在远程TeamCity服务器上运行构建并发送反馈。

We installed TeamCity and TFS and they work fine. My question is how are these two supposed to make our workflow efficient? Once I make changes to code on my dev machine, I have to go to TeamCity UI to run the builds and tests? Where is the automation in this.. I am manually doing it anyway... am I missing an important piece here? I can run builds and unit tests on my dev machine too. All developers making changes, need to go to TeamCity UI to build with updated code? I was kind of expecting TeamCity to detect checked in changes to TFS automatically and run builds immediately on the remote TeamCity server and send me feedback.

推荐答案

您需要转到构建触发部分设置并添加新的构建触发器。它可以是版本控制触发器（当在源代码控制中看到新的变化时触发构建），一个构建触发器，当其他构建完成时触发，调度触发器以定期调度等。

You need to go to Build Triggering part of the settings and add a new build trigger. It can be a version control trigger ( which will trigger the build when new changes are seen in the source control), a build trigger which triggers when other builds finish, schedule trigger to schedule it periodically and so on.

>

这篇关于TeamCity - 自动化在哪里的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！