On Tue, 14 Jun 2011 06:22:23 -0500, Zach Pfeffer <[email protected]>
wrote:
> 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.
What does this mean for the hosting of Gerrit though. Does this mean
that Gerrit has to be on a server with enough space to host all the
trees that will be put through review? Is it one tree per-user?
> > 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.
Ok, that sounds like the biggest chunk of work. Are there any standard
extensions to Gerrit to drive some of this?
To me it seems like we need:
* cron job/daemon to poll Gerrit for approved reviews
* This does the test merges and leaves comments on Gerrit if something
doesn't merge
* It then triggers a test build on the build system and waits for the
result. If it fails it leaves a comment on Gerrit linking to the
build record.
* Then we want to add LAVA in to the mix. I think this needs further
discussion before we can include it in the plan as there would seem
to be many open questions.
Thanks,
James
_______________________________________________
linaro-dev mailing list
[email protected]
http://lists.linaro.org/mailman/listinfo/linaro-dev
