I think a lot of projects don't bother to gate, because its far to much work to set up a workable system.
I can think of several projects I've worked on that would benefit from it but haven't because of time/cost of setting it up. If I could just say "solum create project foo" and get it, I'm sure it would be much more used. The same has been said of Unit tests and CI in the past. "We don't need it". When you give someone a simple to use system though, they see its value pretty quickly. Yeah, gerrit and jenkins are a pain to setup. Thats one of the things that might make solum great. That it removes that pain. Kevin ________________________________________ From: Jay Pipes [jaypi...@gmail.com] Sent: Friday, February 14, 2014 2:51 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Solum] Question about Zuul's role in Solum On Thu, 2014-02-13 at 14:18 +0100, Julien Vey wrote: > I agree gating is a great feature but it is not useful for every > project and as Adrian said, not understood by everyone. > I think many Solum users, and PaaS users in general, are > single-project/single-build/simple git worklow and do not care about > gating. This is 100% correct. > I see 2 drawbacks with Zuul : > - Tenant Isolation : How do we allow access on zuul (and jenkins) for > a specific tenant in isolation to the others tenants using Solum. > - Build customization : One of the biggest advantage of Jenkins is its > ecosystem and the many build customization it offers. Using zuul will > prohibit this. Not sure I understand this part... Zuul works *with* Jenkins. It does not replace it. > About Gerrit, I think it is also a little too much. Many users have > their own reviewing system, Pull requests with github, bitbucket or > stash, their own instance of gerrit, or even a custom git workflow. > Gerrit would be a great feature for future versions of Solum. but only > as an optionnal one, we should not force people into it. Completely agreed. Frankly, both Gerrit and Jenkins are a giant pain in the ass to install, maintain, and configure (hmm, which Java/Prolog programs aren't, I wonder?). Basing Solum's *default* workflow on these tools would be a mistake IMO. Best, -jay _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
