Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,740,095 Members 40,743 Now Online
XDA Developers Android and Mobile Development Forum

[GUIDE] Understanding and using Gerrit [Easy+Explained]

Tip us?
 
v_superuser
Old
(Last edited by v_superuser; 3rd February 2014 at 03:45 PM.)
#1  
v_superuser's Avatar
Senior Member - OP
Thanks Meter 1243
Posts: 459
Join Date: Jan 2013
Location: Jammu
Angry [GUIDE] Understanding and using Gerrit [Easy+Explained]

Quote:
So, what happened to me in the past few days was that, I had to submit few patches to gerrit, and I had no idea what to do, where to start, and everything that runs in the mind of a person who first uses gerrit. One simply doesn't gets the whole knowledge he needs to use gerrit at one place, so I decided to make it, so it could be easier for the new users.
So firstly, I'll explain few terms that are important for you to learn before going towards a bit tricky side.

  1. Git - To be precise, git is a code-sharing website/software that allows you to share your project resources you can 'Make Software, better, together'(That's what the tag line says )!

    Now, before I go to gerrit, read this: Major Open Source Projects, like, CyanogenMod, AOKP, OmniROM etc. don't directly accept pull requests and in case you want to make a change in their source for a fix/feature or anything, you need to send them patches over gerrit which are then reviewed by the trusted members of the community and if they find it valuable enough, gets merged into the git repository!
  2. Gerrit(Copying the definition from Wiki) - Gerrit is a free, web-based team software code review tool. Software developers in a team can review each other's modifications on their source code using a Web browser and approve or reject those changes. It integrates closely with Git, a distributed version control system.
    So, now, git and gerrit are so closely related, that a patch verified over gerrit can directly be merged on git without much hassel, also please note that your gerrit and git username must be same.
  3. Pull Requests - Pull requests are sent over Git after you fork a repository, make some changes into it and then want the owner to merge those changes into his repository, and that's how community development and Open Source works.
  4. Patches - In simple terms, any changes you make to repos of Open Source Projects like CM or AOKP and send them over gerrit for code review are called Patches.

How GERRIT works?!


Now, Gerrit is deployed in place of this central repository and adds an additional concept, a store of pending changes. Everyone still fetches from the authoritative repository but instead of pushing back to it, they push to this pending changes location. A change can only be submitted into the authoritative repository and become an accepted part of the project once the change has been reviewed and approved.
I found a nice diagram explaining this over the internet that will clear your doubts(if any ) -



Now few important stuff needs to be setup before proceeding-

Setting up Git:
Debian/Ubuntu:
Code:
Select Code
sudo apt-get install git
Fedora:
Code:
Select Code
yum install git
ArchLinux:
Code:
Select Code
pacman -S git
openSUSE:
Code:
Select Code
zypper install git
Configuring git:
Code:
Select Code
git config --global user.email "your-email@domain.com"
Code:
Select Code
git config --global user.name "your-username"
Setting up SSH Keys(Skip this if you have already set them up) -
Code:
Select Code
cd .ssh
ssh-keygen -t rsa -C "your-email@domain.com"
Now this will create 2 files in ~/.ssh directory as follows:
Quote:
~/.ssh/id_rsa //identification (private) key
~/.ssh/id_rsa.pub //public key
Adding SSH Keys to your Account -
Code:
Select Code
cat /home/username_on_pc/.ssh/id_rsa.pub
This will show up few lines over terminal, copy those and add them into your git profile(I won't explain that, there are many guides for the same)

Now install few packages -
Code:
Select Code
sudo apt-get install python-pip
sudo pip install git-review
Now comes setting up the Gerrit part -


In case of CyanogenMod,
Code:
Select Code
git config --global review.review.cyanogenmod.org.username "gerrit username"
git config --global review.review.cyanogenmod.org.email "email you registered with"
In case of AOKP,
Code:
Select Code
git config --global review.gerrit.aokp.co.username <gerrit username>
git config --global review.gerrit.aokp.co.email <email you registered with>
Making Changes and Submitting Patches -


I'd firstly recommend you to repo sync to grab the full latest source.
Next(Don't make changes before this step) -
Code:
Select Code
repo start <branch> <path to make changes
Example(You need to be in the source directory) -
Code:
Select Code
repo start kitkat packages/apps/Settings
Now after this, go into the folders, make your changes and save them but only the changes in the specified directories(Packages/apps/Settings in this case)!
then
Code:
Select Code
cd packages/apps/Settings
After making changes, for satisfaction, run,
Code:
Select Code
git status
It tells you what files you modified(In Red color ) and shows on which branch you're currently on.
Now, the committing part,
Run:
Code:
Select Code
git add -A
Run git status again, and it'll show the files in green color, telling you that the changes have been added.
Now:
Code:
Select Code
git commit -s
This will commit the changes and open up a Text Editor called NANO. Here you need to edit the commit message that appears at the side of the gerrit window to describe what the patch does.
After writing the commit message, press Ctrl+O and then Enter key to save the commit message and then Ctrl+X to exit the editor. This is the committing part done.
Now submitting the patch -
Code:
Select Code
repo upload .
After this, it will ask you Yes/No twice(For the first time) and once(Everytime next) and you obviously have to hit Y!
Guess what?! Done!
Congratulations, you just learned gerrit and know how you use it. I hope you'll send some nice patches and respect the Open Source.

But, wait, what if there is a merge conflict
Don't worry, there is a nic doc over the internet to help you with this - http://www.mediawiki.org/wiki/Gerrit/resolve_conflict

If you still have doubts, see few examples here or ask on the thread. I'll be happy to hrlp!

Credits -
> Firstly, My Parents
> @galaxyfreak @championswimmer @crossfire77 to introducing me to gerrit.
> AOKP/CM team for hosting useful docs.


Join the HTC Desire 816 Facebook group for all Development Info and Discussion!
The Following 34 Users Say Thank You to v_superuser For This Useful Post: [ Click to Expand ]
 
v_superuser
Old
#2  
v_superuser's Avatar
Senior Member - OP
Thanks Meter 1243
Posts: 459
Join Date: Jan 2013
Location: Jammu
Ok, so you have changes to make to the gerrit commit you just sent? Read on


Ok, it goes easy,
repo start like earlier, make changes, go to the directory where the changes were made(Settings in this case). Now, make sure you go to the patch URL now and copy up the Change ID, which can be done by clicking over it.
Now, git status to spot the changes.
The,
Code:
Select Code
git add -A
and
Code:
Select Code
git commit --amend
^This will tell git that you need to amend an existing commit. Cool, isn't it?
Now, make changes(if any) to the commit message. and then
Code:
Select Code
repo upload .
YES, That's it! The new change will now be at the same URL under Patch Set 2! And will got 3, 4 so on as you make changes.


Join the HTC Desire 816 Facebook group for all Development Info and Discussion!
The Following 11 Users Say Thank You to v_superuser For This Useful Post: [ Click to Expand ]
 
v_superuser
Old
#3  
v_superuser's Avatar
Senior Member - OP
Thanks Meter 1243
Posts: 459
Join Date: Jan 2013
Location: Jammu
Reserved!


Join the HTC Desire 816 Facebook group for all Development Info and Discussion!
The Following 6 Users Say Thank You to v_superuser For This Useful Post: [ Click to Expand ]
 
Powerhouse
Old
#4  
Powerhouse's Avatar
Senior Member
Thanks Meter 1966
Posts: 795
Join Date: Mar 2013
Really a Great work !
The Following User Says Thank You to Powerhouse For This Useful Post: [ Click to Expand ]
 
UtkarshGupta
Old
#5  
Recognized Contributor
Thanks Meter 3549
Posts: 4,285
Join Date: Nov 2012
Location: New Delhi
Great work !

git config --global review.gerrit.omnirom.org.username "gerrit username"
git config --global review.gerrit.omnirom.org.email "email you registered with"

Here are the configs required for omnirom.
The Following 3 Users Say Thank You to UtkarshGupta For This Useful Post: [ Click to Expand ]
 
solomonsunder
Old
#6  
solomonsunder's Avatar
Junior Member
Thanks Meter 1
Posts: 5
Join Date: Aug 2013
Location: Mumbai

 
DONATE TO ME
Unhappy Unable to patch

Quote:
Originally Posted by #Superuser View Post
Ok, so you have changes to make to the gerrit commit you just sent? Read on


Ok, it goes easy,
repo start like earlier, make changes, go to the directory where the changes were made(Settings in this case). Now, make sure you go to the patch URL now and copy up the Change ID, which can be done by clicking over it.
Now, git status to spot the changes.
The,
Code:
Select Code
git add -A
and
Code:
Select Code
git commit --amend
^This will tell git that you need to amend an existing commit. Cool, isn't it?
Now, make changes(if any) to the commit message. and then
Code:
Select Code
repo upload .
YES, That's it! The new change will now be at the same URL under Patch Set 2! And will got 3, 4 so on as you make changes.
When I do the above commands to provide a patch to CyanogenMod gerrit it gives a new Change-ID and got committed as a new 'Merge Commit'. Can you tell me where I am going wrong?
 
v_superuser
Old
#7  
v_superuser's Avatar
Senior Member - OP
Thanks Meter 1243
Posts: 459
Join Date: Jan 2013
Location: Jammu
Quote:
Originally Posted by solomonsunder View Post
When I do the above commands to provide a patch to CyanogenMod gerrit it gives a new Change-ID and got committed as a new 'Merge Commit'. Can you tell me where I am going wrong?
You sure that you ran git commit --amend ?


Join the HTC Desire 816 Facebook group for all Development Info and Discussion!
The Following User Says Thank You to v_superuser For This Useful Post: [ Click to Expand ]
 
solomonsunder
Old
#8  
solomonsunder's Avatar
Junior Member
Thanks Meter 1
Posts: 5
Join Date: Aug 2013
Location: Mumbai

 
DONATE TO ME
Default patchset

Quote:
Originally Posted by #Superuser View Post
You sure that you ran git commit --amend ?
Yes. I tried to follow your post and this one wiki.cyanogenmod.org/w/Doc:_using_gerrit. I did a change earlier here. review.cyanogenmod.org/#/c/59083/ for a new translation. Since there were whitespace errors and a file strings.xml~ got added, I changed my local file, deleted the strings.xml~, did a git add strings.xml. Then I did a git commit --amend which gave me a new Change-ID which said Merge commit 'refs/changes/83/59083/1' of review.cyanogenmod.org/CyanogenMod/android_frameworks_base into SystemUITamil. Then I did a repo upload. This got uploaded as review.cyanogenmod.org/#/c/59286/

I tried to manually change the Change-ID to I52f02ea81fa7e20334e7ac7f26d37ced6fe54489 and then do a repo upload. But it didn't allow me and gave a message ! [remote rejected] SystemUITamil -> refs/for/cm-11.0 (squash commits first)

Where am I going wrong?
The Following User Says Thank You to solomonsunder For This Useful Post: [ Click to Expand ]
 
solomonsunder
Old
#9  
solomonsunder's Avatar
Junior Member
Thanks Meter 1
Posts: 5
Join Date: Aug 2013
Location: Mumbai

 
DONATE TO ME
Thumbs up Rebase worked

Quote:
Originally Posted by #Superuser View Post
You sure that you ran git commit --amend ?
I did a rebase on frameworks/base and then followed your steps. Now it is working fine. I used to do a repo start branchname projectpath even for patches. Could that have been a reason it was creating new changes?
 
v_superuser
Old
#10  
v_superuser's Avatar
Senior Member - OP
Thanks Meter 1243
Posts: 459
Join Date: Jan 2013
Location: Jammu
Quote:
Originally Posted by solomonsunder View Post
I did a rebase on frameworks/base and then followed your steps. Now it is working fine. I used to do a repo start branchname projectpath even for patches. Could that have been a reason it was creating new changes?
I never actually close the Terminal after submitting a patch and verifying it, so not sure, maybe it lost track of the changes you made and the change that got uploaded. Rebase is actually useful in this. Glad that you figured it out.


Join the HTC Desire 816 Facebook group for all Development Info and Discussion!

The Following 2 Users Say Thank You to v_superuser For This Useful Post: [ Click to Expand ]
Tags
easy, gerrit, guide, how to, steps
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes