Thanks Stephen.

Someone in the community must know

[Kohsuke?  rtyler?, redsolo?]

Regards,

Andrew

On 18 February 2012 10:21, Stephen Connolly <[email protected]
> wrote:

> I wish I knew the answer. You should download an eval version of Jenkins
> enterprise... I normally wouldn't pay for anything, but seriously, the rbac
> plugin is one of our killer features ;-) anything else is a management
> pain... The roles plugin takes about 5% of the pain away... If you have no
> other choice you'll likely be forced to fall back to that ;-)
>
> Sent from my iPhone
>
> On 17 Feb 2012, at 22:26, Andrew Gray <[email protected]> wrote:
>
> Thank you Stephen,
>
> I'll add this knowledge to my databank ;)  Client is a Java-shop.
> Unfortunately they won't pay for anything (in the 8 years I've been there I
> have seen them buy one (little) software licence - pd4ml.)
>
> What authentication scheme is J-On-J using?  Is it Matrix-based with the
> Roles plugin?
>
> Kind Regards,
>
> Andrew Gray
>
> On 17 February 2012 19:18, Stephen Connolly <
> [email protected]> wrote:
>
>> Andrew,
>>
>> [off-list]
>>
>> You might find two cloudbees plugins really useful.
>>
>> CloudBees Folders plugin (currently for paying customers, but soon will
>> be available free (registration required)) makes organising lots of jobs. A
>> lot better
>>
>> CloudBees RBAC plugin (unfortunately no plans for making this one free in
>> the near future) I may be biased, having written it myself, but I think it
>> is the best solution for an authorisation strategy... You can try the
>> evaluation version free for 30 days... The only danger being once you try
>> it you may not want to use any of the others ;-)
>>
>> Stephen.
>>
>>
>> On Friday, 17 February 2012, Andrew Gray <[email protected]>
>> wrote:
>> > Hi,
>> >
>> > I have a client that has a single master with no authentication set up
>> at all currently.
>> >
>> > Issue 1: Anyone can do anything.  Obviously this is bad
>> > Issue 2: LOTS of jobs, LOTS of views...all too unweildy
>> >
>> > I think the perfect solution is to:
>> > 1. Use the Project Based Matrix plugin so that people would only see
>> the jobs related to the projects they are working on.
>> > 2. Create some roles; Admin, Builder, ReadOnly Committer....QED
>> >
>> > Jenkin-On-Jenkins is locked down, how is it doing it?  LDAP, AD,
>> Matrix-based.
>> >
>> > My login (apgray) does not have access to the J-On-J Manage Jenkins
>> page.
>> >
>> > I am currently assuming J-On-J is using Matrix-based security.  Is that
>> correct?  Could someone please confirm.
>> >
>> > If it is good enough for J-On-J it is good enough for the client.
>> >
>> > Regards,
>> >
>> > Andrew
>> >
>>
>
>

Reply via email to