On Wednesday 19 February 2014 13:05:23 Josef Reidinger wrote:

On Wed, 19 Feb 2014 13:02:39 +0100

Sascha Peilicke wrote:

...

Hi guys,

since more and more openSUSE projects start to make use of our CI infrastructure, we have to organize who's allowed to do what. In the past we just added more and more people with rights to organize everything. So I tried to reduce the global list of users with admin rights. Instead, we now have a per-project (translates to Jenkins job) ACL matrix where each project can organize stuff themselves. In simple words, you now can configure per job who's allowed to change things. There should be no need to bug me again :-)

That said, the list of ci.o.o admins now is: coolo, jdsn, bmwiedemann and saschpe (me).

The following openSUSE projects currently use ci.opensuse.org: - Open Build Service / osc - OpenStack - Yast / libyui

The first two projects have per-job based access rules set already. If you have a ci.o.o job and want to grant somebody the right to modify it, just check "Enable project-based security" and add the (already registered) user in question.

And if you want to add your openSUSE-related project to our CI, please get in touch with any of the guys mentioned above. That's it.

Hi Sasche, good idea. Just one question is possible to manage per project nodes? YaST node sometime disapeared and need to be readded, so if we can do it in future ourself ( or if it do not disappear :)

For modifying Jenkins slaves, you need some global rights. As far as I know, you can't really tie a node to a "project" per se. You can only limit where jobs can run. So in practice, some jobs don't care where they are run and thus they may end up on your nodes even. I'm sure there's a plugin to configure this properly. Will have to investigate. Meanwhile, I you can create/edit nodes for yourself. Just don't mess with ours :-) -- With kind regards, Sascha Peilicke SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

On Wednesday 19 February 2014 13:19:45 Josef Reidinger wrote:

On Wed, 19 Feb 2014 13:14:43 +0100

Sascha Peilicke wrote:

...

On Wednesday 19 February 2014 13:05:23 Josef Reidinger wrote:

...

On Wed, 19 Feb 2014 13:02:39 +0100

Sascha Peilicke wrote:

...

Hi guys,

since more and more openSUSE projects start to make use of our CI infrastructure, we have to organize who's allowed to do what. In the past we just added more and more people with rights to organize everything. So I tried to reduce the global list of users with admin rights. Instead, we now have a per-project (translates to Jenkins job) ACL matrix where each project can organize stuff themselves. In simple words, you now can configure per job who's allowed to change things. There should be no need to bug me again :-)

That said, the list of ci.o.o admins now is: coolo, jdsn, bmwiedemann and saschpe (me).

The following openSUSE projects currently use ci.opensuse.org: - Open Build Service / osc - OpenStack - Yast / libyui

The first two projects have per-job based access rules set already. If you have a ci.o.o job and want to grant somebody the right to modify it, just check "Enable project-based security" and add the (already registered) user in question.

And if you want to add your openSUSE-related project to our CI, please get in touch with any of the guys mentioned above. That's it.

Hi Sasche, good idea. Just one question is possible to manage per project nodes? YaST node sometime disapeared and need to be readded, so if we can do it in future ourself ( or if it do not disappear :)

For modifying Jenkins slaves, you need some global rights. As far as I know, you can't really tie a node to a "project" per se. You can only limit where jobs can run. So in practice, some jobs don't care where they are run and thus they may end up on your nodes even. I'm sure there's a plugin to configure this properly. Will have to investigate. Meanwhile, I you can create/edit nodes for yourself. Just don't mess with ours :-)

Thanks a lot. It really helps to help us to fix quickly if node disappear from nodes list.

It is noteworthy that is is actually a Jenkins bug. I'll try to debug it once I got the time. -- With kind regards, Sascha Peilicke SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nuernberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org