And we already reached the next step: Changes in RAP Runtime are now verified by a new Hudson job rap-head-runtime-gerrit on our HIPP instance. The job is triggered by Gerrit and runs a full (Tycho/Maven) build including tests. If the job finishes successfully, Hudson will vote with a verify +1.
This all turns out to be much easier than I expected. Maybe we should consider enabling Gerrit for our RAP Incubator repositories, too. [1] https://hudson.eclipse.org/rap/job/rap-head-runtime-gerrit/ Thanks, Markus On Thu, Dec 12, 2013 at 9:37 AM, Ralf Sternberg < [email protected]> wrote: > Hi RAP devs, > > Eclipse projects are encouraged to use Gerrit and we decided to give it a > try. > > Gerrit offers some advantages such as being able to peer-review changes > *before* they go into the repo and getting rid of these patches in the RC > phase. We can use inline comments to communicate suggestion more easily, > and this will hopefully make it easier for contributors as well. > > On the other hand, Gerrit also induces some overhead to our process. We'll > have to gain some experience to understand whether this a problem or not. > If it is, there's still an option to bypass the review process. > > Gerrit is now installed on our two main repositories, rap, and rap.tools. > The RAP Incubator repositories are not affected. Details on how to setup > our environments for Gerrit can be found in the Eclipse Wiki [1]. Let's see > how it works out! > > Regards, > Ralf > > [1] http://wiki.eclipse.org/Gerrit#Gerrit_setup > > > _______________________________________________ > rap-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/rap-dev > >
_______________________________________________ rap-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/rap-dev
