gerrit使用總結

gerrit仍是輕易不要嘗試引入，它的權限管理，真是複雜極了。對於小型團隊，初期這將是個噩夢，可是對於像OpenStack，安卓這種大型team，又是一把利器。

 

下面嘗試測試了兩個用戶的簡單狀況，不少配置都是系統默認，沒有進行啥複雜配置，即便這樣也是錯誤百出，光一個commit就要折騰半天，並且還有些機制沒搞清楚。

 

首先要作的準備工做就是準備兩個gerrit用戶，user1和user2，而且分別把user1和user2的ssh pub-key經過gerrit setting添加好。

 

1. 首先user1建立一個叫HelloWord的project。

 

   如何建立project請參考前期博客或者官方文檔。

 

2. user1在本身的工做環境中把HelloWord clone下來

 

[user1@jenkins ~]$ git clone ssh://user1@gerrit.example.com:29418/HelloWorld.git
Initialized empty Git repository in /home/user1/HelloWorld/.git/
remote: Counting objects: 2, done
remote: Finding sources: 100% (2/2)
remote: Total 2 (delta 0), reused 0 (delta 0)
Receiving objects: 100% (2/2), done.
加入user1沒有添加ssh pubkey的話，這一步會出permission deny

clone後，建立一個README文件並add，commit
[user1@jenkins ~]$ cd HelloWorld
[user1@jenkins HelloWorld]$ ls
[user1@jenkins HelloWorld]$ touch README
[penxiao@jenkins test]$ git add README 
[penxiao@jenkins test]$ git commit -m add README
這裏注意一點，在下面要push以前，必定要配置好git config的 username和email
能夠經過命令行或者直接編輯 ~/.gitconfig文件實現，並且email必定要和gerrit裏註冊的email一致，否者push也會出錯。
[user1@jenkins HelloWorld]$ git push origin master
Counting objects: 3, done.
Writing objects: 100% (3/3), 213 bytes, done.
Total 3 (delta 0), reused 0 (delta 0)
remote: Processing changes: refs: 1, done    
To ssh://user1@gerrit.example.com:29418/HelloWorld.git
 * [new branch]      master -> master
[user1@jenkins HelloWorld]$

在gerrit的gitweb連接能夠查看push的文件。

 

3. user2加入

 

[user2@jenkins ~]$ git clone ssh://user1@gerrit.example.com:29418/HelloWorld.git

Initialized empty Git repository in /home/user2/HelloWorld/.git/

remote: Counting objects: 3, done

remote: Finding sources: 100% (3/3)

remote: Total 3 (delta 0), reused 3 (delta 0)

Receiving objects: 100% (3/3), done.

[user2@jenkins ~]$ cd HelloWorld

[user2@jenkins HelloWorld]$ ls

README

[user2@jenkins HelloWorld]$ 

 

user2對README文件進行修改，而後要commit，push

！！！也一樣注意，user2的git config，username和email的配置，email要和gerrit setting裏的一致。

 

commit完之後能夠看到

 

[user2@jenkins HelloWorld]$ git log

commit 7959fe47bc2d2f53539a1861aa6b0d71afe0a531

Author: user2 <user2@gerrit.com>

Date:   Thu Dec 12 00:24:53 2013 -0500

 

    edit README

 

commit 98099fc0de3ba889b18cf36f9a5af267b3ddb501

Author: user1 <user@gerrit.com>

Date:   Thu Dec 12 00:15:08 2013 -0500

 

    add README

[user2@jenkins HelloWorld]$

 

如今user2要把此次的改變push到gerrit，能夠麼？

不行的，能夠看到

[user2@jenkins HelloWorld]$ git push origin master

Counting objects: 5, done.

Writing objects: 100% (3/3), 249 bytes, done.

Total 3 (delta 0), reused 0 (delta 0)

remote: Branch refs/heads/master:

remote: You are not allowed to perform this operation.

remote: To push into this reference you need 'Push' rights.

remote: User: user2

remote: Please read the documentation and contact an administrator

remote: if you feel the configuration is incorrect

remote: Processing changes: refs: 1, done    

To ssh://user2@gerrit.example.com:29418/HelloWorld.git

 ! [remote rejected] master -> master (prohibited by Gerrit)

error: failed to push some refs to 'ssh://user2@gerrit.example.com:29418/HelloWorld.git'

[user2@jenkins HelloWorld]$ 

 

這就是gerrit的精髓所在了。緣由是gerrit不容許直接將本地修改同步到遠程倉庫。客戶機必須先push到遠程倉庫的refs/for/*分支上，等待審覈。這也是爲何咱們須要使用gerrit的緣由。gerrit自己就是個代碼審覈工具。

 

接下來更該push的地址：  

[user2@jenkins HelloWorld]$git config remote.origin.push refs/heads/*:refs/for/*  

 

此命令實際是更改的是本地倉庫test_project/.git/config文件。 

再次push   

[user2@jenkins HelloWorld]$git push origin  

此次不要加master

[user2@jenkins HelloWorld]$ git push origin

Counting objects: 5, done.

Writing objects: 100% (3/3), 249 bytes, done.

Total 3 (delta 0), reused 0 (delta 0)

remote: Processing changes: refs: 1, done    

remote: ERROR: missing Change-Id in commit message footer

remote: Suggestion for commit message:

remote: edit README

remote: 

remote: Change-Id: I7959fe47bc2d2f53539a1861aa6b0d71afe0a531

remote: 

remote: Hint: To automatically insert Change-Id, install the hook:

remote:   gitdir=$(git rev-parse --git-dir); scp -p -P 29418 user2@gerrit.example.com:hooks/commit-msg ${gitdir}/hooks/

remote: 

remote: 

To ssh://user2@gerrit.example.com:29418/HelloWorld.git

 ! [remote rejected] master -> refs/for/master (missing Change-Id in commit message footer)

error: failed to push some refs to 'ssh://user2@gerrit.example.com:29418/HelloWorld.git'

 

尼瑪，仍是不行，說缺change-Id，爲了能讓每次commit能本身insert 這個change-id，須要從gerrit server上下載一個腳本

 

[user2@jenkins HelloWorld] scp -p 29418 user2@gerrit.example.com:hooks/commit-msg <local path to your git>/.git/hooks/

 

而後從新commit

[user2@jenkins HelloWorld]$ git commit --amend

再次查看git log

[user2@jenkins HelloWorld]$ git log

commit f6b5919170875b5b4870fca2ab906c516c97006e

Author: user2 <user2@gerrit.com>

Date:   Thu Dec 12 00:24:53 2013 -0500

 

    edit by user2

    

     Change-Id: Ieac68bebefee7c6d4237fa5c058386bf7c4f66b7

 

commit 98099fc0de3ba889b18cf36f9a5af267b3ddb501

Author: user1 <user1@gerrit.com>

Date:   Thu Dec 12 00:15:08 2013 -0500

 

    add README

[user2@jenkins HelloWorld]$ 

 

此次就有了change id

而後再次push

[user2@jenkins HelloWorld]$ git push origin

Counting objects: 5, done.

Writing objects: 100% (3/3), 289 bytes, done.

Total 3 (delta 0), reused 0 (delta 0)

remote: Processing changes: new: 1, refs: 1, done    

remote: 

remote: New Changes:

remote:   http://gerrit.example.com:8080/1

remote: 

To ssh://user2@gerrit.example.com:29418/HelloWorld.git

 * [new branch]      master -> refs/for/master

[user2@jenkins HelloWorld]$ 

 

終於尼瑪成功了！！！