[英]Gitflow - who tests master branch and who tests release branch
I want to propose Gitflow for our new web application. 我想为我们的新Web应用程序提出Gitflow。 We have QA environment where product acceptance testing is done before release.
我们有QA环境,产品验收测试在发布之前完成。 I want to know which branch should be deployed to QA - release branch or master?
我想知道应该将哪个分支部署到QA - 发布分支或主分支? Which branch should be deployed to production?
应该将哪个分支部署到生产中? If we deploy and test the release branch and then merge it back to master who will test master?
如果我们部署并测试发布分支,然后将其合并回主人谁将测试主人?
The release
branch is meant to be sent through QA validation and deployment process. release
分支旨在通过QA验证和部署过程发送。
So your release
branch would be sent to QA environment. 因此,您的
release
分支将被发送到QA环境。 Once validation is complete, release
branch would be deployed. 验证完成后,将部署
release
分支。 Once deployment is successful, release
branch would be merged into master
. 部署成功后,
release
分支将合并到master
。
master
should always represent the code that is currently running on production. master
应始终代表当前在生产中运行的代码。 That way if you needed to issue a hotfix while the current release
branch is being validated, you could branch off of master
. 这样,如果您需要在验证当前
release
分支时release
修补程序,则可以从master
分支。 Or if for some reason you needed to redeploy a production instance you would deploy master
. 或者,如果由于某种原因需要重新部署生产实例,则需要部署
master
。
want to know which branch should be deployed to QA - release branch or master?
想知道应该将哪个分支部署到QA - 发布分支还是主分支?
I would argue release
: QA should test what comes before what you end up deploying. 我认为
release
:QA应该测试你最终部署之前的内容。
Which branch should be deployed to production?
应该将哪个分支部署到生产中?
master
, the one where you tag the release with its name. master
,用你的名字标记版本的那个。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.