Proposal to adding new 'project job power users' to jenkins.ovirt.org
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@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? Eyal Edri.
Recently i've been asked for various jobs or settings on jenkins.ovirt.= org. =20 These are specific project related jobs for an ovirt project (this time= it was 'vdsm'). =20 I want to propose that we'll assign 'power users' per project, so reque= sts won't hold back in queue (i'm not always available and it will take t= ime until we'll have more people helping out in infra). =20 power users will have permissions to: =20 1. configure jobs 2. create jobs 3. run jobs 4. trigger gerrit manual=20 =20 they WON'T be able to: =20 1. add/configure slaves 2. manage jenkins configuration 3. delete jobs 4. install plugins. =20 =20 to start things going, i propose Saggi Mizrahi (smizrahi@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=
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig0ECE59F3F975B5D53BDFEB5B Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 11/14/2012 09:11 AM, Eyal Edri wrote: past.
=20 =20 thoughts?=20
+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." - Karsten --=20 Karsten 'quaid' Wade, Sr. Analyst - Community Growth http://TheOpenSourceWay.org .^\ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41 --------------enig0ECE59F3F975B5D53BDFEB5B Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iD8DBQFQo9L92ZIOBq0ODEERAteQAJ0ZHuAYNh/tjCIQIhmekp7kUM19kQCfUKYb 0cYS04MIztRszZuDymixYcM= =rRD4 -----END PGP SIGNATURE----- --------------enig0ECE59F3F975B5D53BDFEB5B--
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@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.
----- Original Message -----
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@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 on everything , Sounds like a good solution.
Eyal Edri.
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
On 11/14/2012 07:11 PM, 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@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?
Eyal Edri.
+1 to delegating.
On 11/14/2012 09:45 PM, Itamar Heim wrote:
On 11/14/2012 07:11 PM, 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@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?
Eyal Edri.
+1 to delegating.
I think this move will actually help to develop our testing framework on two perspectives: -infra level -specific components testing i think a much higher level can be reached on both using this delegation + lowering the load on specific people. big +1.
Seems like there is approval from most people and no rejections. therefore saggi has now power user permissions on jenkins.ovirt.org. congrats! we'll can discuss on proposal for power users from other projects on infra or ovirt weekly meetings. Eyal. ----- Original Message -----
From: "Moran Goldboim" <mgoldboi@redhat.com> To: "Itamar Heim" <iheim@redhat.com> Cc: "Eyal Edri" <eedri@redhat.com>, "infra" <infra@ovirt.org>, "Dan Kenigsberg" <danken@redhat.com>, "Saggi Mizrahi" <smizrahi@redhat.com> Sent: Wednesday, November 14, 2012 9:49:45 PM Subject: Re: Proposal to adding new 'project job power users' to jenkins.ovirt.org
On 11/14/2012 09:45 PM, Itamar Heim wrote:
On 11/14/2012 07:11 PM, 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@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?
Eyal Edri.
+1 to delegating.
I think this move will actually help to develop our testing framework on two perspectives: -infra level -specific components testing
i think a much higher level can be reached on both using this delegation + lowering the load on specific people. big +1.
participants (6)
-
Ewoud Kohl van Wijngaarden -
Eyal Edri -
Itamar Heim -
Karsten 'quaid' Wade -
Moran Goldboim -
Ofer Schreiber