GitHub,Gerrit,Hudson(Jenkins)工作流 [英] GitHub, Gerrit, Hudson(Jenkins) workflow
问题描述
我刚刚开始使用GitHub,Gerrit和Hudson(Jenkins)。我需要对工作流程有一些想法。
I'm just getting started using GitHub, Gerrit, and Hudson(Jenkins) together. And I need some thoughts on workflow.
我们想使用GitHub作为我们的主要远程仓库。我们想使用Gerrit主要用于代码审查,但也用于Hudson的构建触发器。
We'd like to use GitHub as our main remote repo. We'd like to use Gerrit primarily for code reviews, but also for build triggers in Hudson.
现在,我有一些麻烦思考工作流程,并希望听到别人做了自己。
At the moment, though, I'm having some trouble thinking through the workflow for this and would like to hear what others have done themselves. Thoughts?
推荐答案
我没有直接使用Gerrit,但我喜欢中间和专门的repo之间的想法:
I haven't directly used Gerrit, but I like the idea of intermediate and specialized repo between:
- 您的开发者资源库
- 中央GitHub远程仓库
所以你需要确定你要在远程GitHub仓库中发布什么:
So you need to determine what you want to publish in the remote GitHub repo:
- (意味着本地Gerrit webapp会拉动GitHub代码来检查)
- 已经审核的代码(意味着您首先发布提交到Gerrit的代码,在代码审核之后,您推送他们到GitHub)
第二个工作流程更接近 Google Android Projects后跟Gerrit 。
The second workflow is closer to what Google Android Projects follows with Gerrit.
在这两种情况下,
这篇关于GitHub,Gerrit,Hudson(Jenkins)工作流的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!