group feature added to r10919

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

group feature added to r10919

szczepiq
Hi,

I merged our group feature to the the revision 10919 in
/branches/btosabre/hudson/main

I would appreciate if someone could have a look and tell us if this is
something you would be interested in merging in. We are happy to
change whatever you like if you find some features unnecessary/wrong.
Also, please let me know if you're not interested in this
functionality.

Few words about the functionality. We have centralized CI architecture
(few hudsons, lots of slave jobs) so we needed some means of grouping
jobs and people. Mainly for reducing the noise - a team (a group) can
see only their jobs but also for security - one team should not mess
with other teams' jobs (and for that we wrote group based security
plugin).

Cheers,
Szczepan Faber

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: group feature added to r10919

Eric Lefevre-Ardant
Hi Szczepan,

Though I do not have a need for this currently, one of my colleagues mentioned recently that it was one of the great features of LuntBuild. For him, that's the main reason his client was not using Hudson.

So it definitely seems like a very worthwhile feature.

Eric

On 22/07/2008, szczepiq <[hidden email]> wrote:
Hi,

I merged our group feature to the the revision 10919 in
/branches/btosabre/hudson/main

I would appreciate if someone could have a look and tell us if this is
something you would be interested in merging in. We are happy to
change whatever you like if you find some features unnecessary/wrong.
Also, please let me know if you're not interested in this
functionality.

Few words about the functionality. We have centralized CI architecture
(few hudsons, lots of slave jobs) so we needed some means of grouping
jobs and people. Mainly for reducing the noise - a team (a group) can
see only their jobs but also for security - one team should not mess
with other teams' jobs (and for that we wrote group based security
plugin).

Cheers,
Szczepan Faber

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]


Reply | Threaded
Open this post in threaded view
|

Re: group feature added to r10919

Aleksandar Kostadinov
I think that security currently is a hard goal for hudson. But for
somebody that needs to stay safe, I think auditing would be much more
easily achievable. For example log to an external log server when and
who did some particular operation.

Eric Lefevre wrote, On 07/22/2008 12:28 PM (EEST):

> Hi Szczepan,
>
> Though I do not have a need for this currently, one of my colleagues
> mentioned recently that it was one of the great features of LuntBuild.
> For him, that's the main reason his client was not using Hudson.
>
> So it definitely seems like a very worthwhile feature.
>
> Eric
>
> On 22/07/2008, *szczepiq* <[hidden email]
> <mailto:[hidden email]>> wrote:
>
>     Hi,
>
>     I merged our group feature to the the revision 10919 in
>     /branches/btosabre/hudson/main
>
>     I would appreciate if someone could have a look and tell us if this is
>     something you would be interested in merging in. We are happy to
>     change whatever you like if you find some features unnecessary/wrong.
>     Also, please let me know if you're not interested in this
>     functionality.
>
>     Few words about the functionality. We have centralized CI architecture
>     (few hudsons, lots of slave jobs) so we needed some means of grouping
>     jobs and people. Mainly for reducing the noise - a team (a group) can
>     see only their jobs but also for security - one team should not mess
>     with other teams' jobs (and for that we wrote group based security
>     plugin).
>
>     Cheers,
>     Szczepan Faber
>
>     ---------------------------------------------------------------------
>     To unsubscribe, e-mail: [hidden email]
>     <mailto:[hidden email]>
>     For additional commands, e-mail: [hidden email]
>     <mailto:[hidden email]>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: group feature added to r10919

Kohsuke Kawaguchi
Administrator
In reply to this post by szczepiq
szczepiq wrote:

> Hi,
>
> I merged our group feature to the the revision 10919 in
> /branches/btosabre/hudson/main
>
> I would appreciate if someone could have a look and tell us if this is
> something you would be interested in merging in. We are happy to
> change whatever you like if you find some features unnecessary/wrong.
> Also, please let me know if you're not interested in this
> functionality.
>
> Few words about the functionality. We have centralized CI architecture
> (few hudsons, lots of slave jobs) so we needed some means of grouping
> jobs and people. Mainly for reducing the noise - a team (a group) can
> see only their jobs but also for security - one team should not mess
> with other teams' jobs (and for that we wrote group based security
> plugin).
>
> Cheers,
> Szczepan Faber
This is something that I'd like to merge to the trunk.

Can you describe the funtionality a little more? Does it resolve issue
#2096 <https://hudson.dev.java.net/issues/show_bug.cgi?id=2096>? Or is
it mostly about controlling the visibility of jobs? Or does it do both?
Or more?


--
Kohsuke Kawaguchi
Sun Microsystems                   http://weblogs.java.net/blog/kohsuke/

smime.p7s (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: group feature added to r10919

szczepiq
Hi,

> Can you describe the funtionality a little more? Does it resolve issue #2096
> <https://hudson.dev.java.net/issues/show_bug.cgi?id=2096>? Or is it mostly
> about controlling the visibility of jobs? Or does it do both? Or more?

Have a look at attached screenshots. It's about visibility and also
about making it possible to write group based authorization strategy
plugin.

I don't think our 'Group' feature matches the requirements of issue
#2096. #2096 is a natural improvement of matrix-based security.
Currently in MBS there is a notion of "User/group" but it is not used
(BTW I think it should be a user/role rather than a user/group). Maybe
it's time to add a 'role' field to a user form. The value from this
field could be used for configuring MBS.

Our 'Group' feature is about grouping people and jobs. Think of a
group as of a project: people + jobs that build/test the software they
create).

One more feature that is also included in r10919 is 'My views' (e.g.
the user can create her own views - it goes along with the vision of
Hudson personalization). It was easier to do the merge this way
because we got the green light for contributing our changes quite
late. Let me know if you'd like this functionality in or out - I can
prepare separate revisions.

Cheers,
Szczepan Faber

On Wed, Jul 23, 2008 at 12:02 AM, Kohsuke Kawaguchi
<[hidden email]> wrote:

> szczepiq wrote:
>>
>> Hi,
>>
>> I merged our group feature to the the revision 10919 in
>> /branches/btosabre/hudson/main
>>
>> I would appreciate if someone could have a look and tell us if this is
>> something you would be interested in merging in. We are happy to
>> change whatever you like if you find some features unnecessary/wrong.
>> Also, please let me know if you're not interested in this
>> functionality.
>>
>> Few words about the functionality. We have centralized CI architecture
>> (few hudsons, lots of slave jobs) so we needed some means of grouping
>> jobs and people. Mainly for reducing the noise - a team (a group) can
>> see only their jobs but also for security - one team should not mess
>> with other teams' jobs (and for that we wrote group based security
>> plugin).
>>
>> Cheers,
>> Szczepan Faber
>
> This is something that I'd like to merge to the trunk.
>
> Can you describe the funtionality a little more? Does it resolve issue #2096
> <https://hudson.dev.java.net/issues/show_bug.cgi?id=2096>? Or is it mostly
> about controlling the visibility of jobs? Or does it do both? Or more?
>
>
> --
> Kohsuke Kawaguchi
> Sun Microsystems                   http://weblogs.java.net/blog/kohsuke/
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

adding new job.png (235K) Download Attachment
adding users to group.png (227K) Download Attachment
dashboard.png (359K) Download Attachment
group status.png (233K) Download Attachment