本文介绍了Git是否支持“复制到"?标签?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我认为这个问题需要一些背景知识,因为在git中可能有更好的方法.

I think this question requires a bit of background, as there may be a better way to do this in git.

我有一个构建服务器,可以对我们的主要开发分支进行持续集成.这很好用,并且显然一直在寻找更改并建立该特定分支.

I have a build server that does continuous integration for our main development branch. This works great, and is obviously always looking for changes and building that specific branch.

我还有一个QA构建,我们想按需构建和部署.过去,当我使用SVN时,我们将创建一个名为"QA"的标签,我们只需将正确的修订版本复制到要部署QA构建的位置即可.我们将重新使用QA标签,这使我们可以将构建配置指向此标签.

I also have a QA build, that we want to build and deploy on demand. In the past, when I used SVN, we would create a tag called "QA", which we would simply copy the correct revision to when we wanted to deploy a QA build. We would re-use the QA tag, and this allowed us to point the build configuration at this tag.

我要避免的是在部署质量检查时必须更改构建配置.分支不喜欢这种正确答案.

What I want to avoid is having to change the build configuration when it comes time to deploy QA. A branch doesn't "feel" like the right answer for this.

我如何在git中实现这一目标而又不产生大量进程开销?

How would I achieve this in git without incurring a lot of process overhead?

推荐答案

我同意 bdesham :如果您按下正确提交到专用的QA分支,您的构建计划程序可以监视该分支,并确保根据正确的提交(最后一个推送到该QA分支)进行构建.

I agree with bdesham: if you push the right commit to a dedicated QA branch, your build scheduler can monitor that branch and be sure to build against the right commit (the last one pushed to that QA branch).

这篇关于Git是否支持“复制到"?标签?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!

09-12 08:23