On Tue, 23 Sep 2014 12:48:54 +0200
<chru...@suse.cz> wrote:

> Hi!
> > > But given the fact that this setup is less tested it tends to
> > > break occasionally :(
> > > 
> > 
> > Using Gerrit and Jenkins this would be solvable, but then you need
> > to find a host that supports this combination. Not use if
> > gerrithub.io does this.
> 
> That sounds like an interesting idea. Maybe we just need a github
> jenkins plugin to have it start a build for each push and send an
> email to the mailing list if it failed. But I have not idea how to
> setup such system :(
> 

The good thing with Gerrit is that it builds a commit queue, and you
can say no to a commit in the commit queue. Either because the testing
didn't pass, or because the review didn't pass. It also handles the
case when you retry a commit, knowing that this is the new attempt for
the same fix rather than a new unique commit.

Not sure how dependencies between commits are handled though. This is
probably meant to be detected by testing (or verification in Gerrit
language...).

I haven't tried Gerrit myself, only read about it. But it seems quite
nice. There is less risk for errors for those contributing, since all
they do is pushing to send commits. They need to install a hook into
their Git installation though, so that Gerrit can track when you send
further commits for the same fix.

/Mats

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

Reply via email to