|
Hi all,
It's been already months since we chatted about this.
I didn't attend many WTP calls. Was a decision taken regarding
move to Gerrit?
Cheers,
On 10/07/2014 04:33 PM, Mickael Istria wrote:
So
the steps for Java EE would be:
1. Open a bug against the Eclipse Foundation > Community >
Gerrit component ( https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Community&component=Gerrit
) asking for usage of Gerrit for your project repository. Specify
on the bug that for the moment you'd like to keep the ability for
committers to push directly and to be able to bypass review. This
requires project lead to give a +1. Here is an example: https://bugs.eclipse.org/bugs/show_bug.cgi?id=421975
2. After webmaster processed your request, the current Git repo
becomes read-only. So in order to be able to push, you'll need to
update to the new Gerrit repo URLs such as ssh://user@xxxxxxxxxxxxxxx:29418/jeetools/webtools.javaee.git
3. If you use SSH you'll need to upload your public key to Gerrit:
https://git.eclipse.org/r/#/settings/ssh-keys
4. Configure notifications to be informed of incoming reviews by
watching the jeetools/webtools.javaee project: https://git.eclipse.org/r/#/settings/projects
And IIRC that's all. Then committers can directly push to the repo
as they're used to -just the underlying URL is different-, and
contributors (and committers who want to get code reviewed before
merging) can push with "git push gerrit HEAD:refs/for/master".
This JSDT wiki page shows the instructions for contributors to
push a change for review: https://wiki.eclipse.org/JSDT/Development#Gerrit_Reviews
A next step would be to set up jobs to have Hudson validation
Gerrit patches, but this can be done in a next iteration.
|
