Proposal to adding new 'project job power users' to jenkins.ovirt.org

[Ewoud Kohl van Wijngaarden]

On Wed, Nov 14, 2012 at 09:21:00AM -0800, Karsten 'quaid' Wade wrote:
> On 11/14/2012 09:11 AM, Eyal Edri wrote:
> > Recently i've been asked for various jobs or settings on
> > jenkins.ovirt.org.
> >
> > These are specific project related jobs for an ovirt project (this
> > time it was 'vdsm').
> >
> > I want to propose that we'll assign 'power users' per project, so
> > requests won't hold back in queue (i'm not always available and it
> > will take time until we'll have more people helping out in infra).
> >
> > power users will have permissions to:
> >
> > 1. configure jobs
> > 2. create jobs
> > 3. run jobs
> > 4. trigger gerrit manual
> >
> > they WON'T be able to:
> >
> > 1. add/configure slaves
> > 2. manage jenkins configuration
> > 3. delete jobs
> > 4. install plugins.
> >
> >
> > to start things going, i propose Saggi Mizrahi (smizrahi at redhat.com)
> > as a power user for VDSM.  saggi has been part of the vdsm project
> > from day 1 and is a very active member of the project since then.
> > he has knowledge in Jenkins and have created and configured jobs in
> > the past.
> >
> >
> > thoughts?
>
> +1 to everything.
>
> If you'd like, when we're decided here, you can ask on arch@ looking for
> 1+ power users from each sub-project.
>
> I think a key ingredient to an open source infrastructure is being able
> to segment administrative functions.
>
> That makes it easier and more likely to give out admin access, since we
> can know it's properly segmented.
>
> Aside from keeping the project safe, it lets people feel safe in taking
> on an admin role. "Oh, even if I mess up royally, the worst that happens
> is really minor and can easily be rolled back."

I can only agree to this. We provide the infra (jenkins, slaves) and
projects manage their jobs.