On 13 June 2011 22:46, James Westby <james.wes...@linaro.org> wrote:
> Hi Zach,
>
> Thanks for the prompt response.
>
> Please asssume that you are talking to someone that has never used
> Gerrit before :-)
>
> On Mon, 13 Jun 2011 20:27:34 -0500, Zach Pfeffer <zach.pfef...@linaro.org> 
> wrote:
>> James,
>>
>> Thanks for jumping on this. The need for Gerrit grows by the day.
>>
>> The first thing I'd want to do would be to log in using my openid and
>> upload my ssh key to it.
>
> Openid is easy I think, I'll make sure it's documented in the RT ticket
> that openid is what we want the service to use for auth.
>
> Is uploading your ssh key a standard part of Gerrit?

Yes. Gerrit uses ssh (I'm not sure if this is configurable) for git
transport between the local repo and the server.

>> Second, I'd want to sync the Android-LEB and push a test change.
>
> What does syncing and pushing involve? I assume they are native parts of
> Gerrit, but do we need to adjust our hosting of the Android trees on
> git.linaro.org to support this?

No, we shouldn't have to adjust our hosting. Take a look at
http://android.git.kernel.org/ where all the Android trees are hosted.

This write up shows the basic workflow:

http://source.android.com/source/version-control.html

This write up documents submitting patches:

http://source.android.com/source/submit-patches.html

>> Third, I'd want to take the test change through the Gerrit lifecycle.
>
> This is just the review cycle that is a standard part of Gerrit?

See submitting patches above.

>> From there I'd want to hook up auto-merging and per-change build validation.
>
> This would take approved changes and attempt to merge them in to a
> staging tree. From there it would do a build test, and then ideally push
> the results through LAVA. If all of that is successful then it would
> replace the current LEB tip with the staging tree and start again?

Yup.

_______________________________________________
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev

Reply via email to