简体繁体 English

TeamCity在Git分支中看不到更改

[英]TeamCity does not see changes in Git branch

原文 2015-05-26 11:14:43 2 1 git/ teamcity-9.0

I have two git branches set up, dev and test. 我设置了两个git分支，即dev和test。 The dev branch is frequently committed to, then periodically merged into test. 开发分支经常被提交，然后定期合并到测试中。 I have a teamcity project set up with the VCS root pointed to dev as the default branch, and test included in the branch specification of the VCS root ( +:refs/heads/test ). 我有一个teamcity项目，其VCS根目录指向dev作为默认分支，并且测试包含在VCS根目录的分支规范中（ +:refs/heads/test ）。 Teamcity picks up changes to the dev branch just fine, but when merging to test, it doesn't detect when the merge is committed and sync'ed. Teamcity可以很好地拾取对dev分支的更改，但是在进行合并测试时，它不会检测到何时提交并同步了合并。 How can I get TeamCity to recognize the push to test and deploy appropriately? 如何使TeamCity认识到适当测试和部署的推动力？

1 个解决方案

Why do you need this test branch? 为什么需要这个测试分支？ What purposes does it serve? 它有什么作用？

If you need it only for deploying to TEST environment maybe tagging a DEV branch is enough? 如果只需要将其部署到TEST环境中，则标记DEV分支就足够了吗？ So instead of merging code to TEST branch (and having TC build fired automatically by this merge) how about just running a build configuration (when you think code is ready for TEST) that will tag a code (with eg version and date) and performs tests, does a deploy or whatever is necessary? 因此，与其将代码合并到TEST分支（并通过此合并自动触发TC构建），不如运行一个构建配置（当您认为代码已准备好进行TEST时），该配置将标记代码（例如版本和日期）并执行测试，部署还是需要什么？

I have multiple DEV builds a day but for QA env we have a weekly builds set up, but it does not require separate branch for code. 我每天有多个DEV构建，但是对于QA env，我们每周都要建立一个构建，但是它不需要单独的分支来编写代码。