Hi!
> > > 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.

I know how it works, but I do not like that it forces particular
workflow. I think that doing automatic git rebuilds, while not ideal,
should be enough for LTP. That way problems would be discovered in a
matter of hours and fixed soon enough.

-- 
Cyril Hrubis
chru...@suse.cz

------------------------------------------------------------------------------
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