Blocking access to the build

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

Blocking access to the build

Jeff Mutonho

Hi

Is there a way of making  it *not*  possible for everyone to schedule a build by  clicking on the "Build Now"  link?

--

"Don't take the name of root in vain."

Jeff  Mutonho
Cape Town
South Africa

GoogleTalk : ejbengine
Skype        : ejbengine
Registered Linux user number 366042
Reply | Threaded
Open this post in threaded view
|

Re: Blocking access to the build

Tom Huybrechts
Enable security ?

On 7/6/07, Jeff Mutonho <[hidden email]> wrote:

>
> Hi
>
> Is there a way of making  it *not*  possible for everyone to schedule a
> build by  clicking on the "Build Now"  link?
>
> --
>
> "Don't take the name of root in vain."
>
> Jeff  Mutonho
> Cape Town
> South Africa
>
> GoogleTalk : ejbengine
> Skype        : ejbengine
> Registered Linux user number 366042

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

Reply | Threaded
Open this post in threaded view
|

Re: Blocking access to the build

Jeff Mutonho


On 7/6/07, Tom Huybrechts <[hidden email]> wrote:
Enable security ?

Yes...basically so that the  person with admin rights is the only one allowed to launch a build by clicking on the "Build now" link.Much like Continuum , where anyone can view the builds  , but in order to configure or launch a build  , one has to login

--

"Don't take the name of root in vain."

Jeff  Mutonho
Cape Town
South Africa

GoogleTalk : ejbengine
Skype        : ejbengine
Registered Linux user number 366042
Reply | Threaded
Open this post in threaded view
|

Re: Blocking access to the build

Tom Huybrechts
Just to be clear: 'Enable security' is a checkbox in the configuration
page which enables what you describe.

Tom

On 7/6/07, Jeff Mutonho <[hidden email]> wrote:

>
>
> On 7/6/07, Tom Huybrechts <[hidden email]> wrote:
> > Enable security ?
> >
> >
> Yes...basically so that the  person with admin rights is the only one
> allowed to launch a build by clicking on the "Build now" link.Much like
> Continuum , where anyone can view the builds  , but in order to configure or
> launch a build  , one has to login
>
> --
>
>
> "Don't take the name of root in vain."
>
> Jeff  Mutonho
> Cape Town
> South Africa
>
> GoogleTalk : ejbengine
> Skype        : ejbengine
> Registered Linux user number 366042

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

Reply | Threaded
Open this post in threaded view
|

Re: Blocking access to the build

Jeff Mutonho


On 7/6/07, Tom Huybrechts <[hidden email]> wrote:
Just to be clear: 'Enable security' is a checkbox in the configuration
page which enables what you describe.

Tom

Lol ...the power of semantics :) .Thanks
--

"Don't take the name of root in vain."

Jeff  Mutonho
Cape Town
South Africa

GoogleTalk : ejbengine
Skype        : ejbengine
Registered Linux user number 366042
Reply | Threaded
Open this post in threaded view
|

RE: Re: Blocking access to the build

tvworks

It would be nice if this was more granular though.  For example, there could be an “admin” user, a “build” user, and a “guest” user all with different permissions.

 


From: Jeff Mutonho [mailto:[hidden email]]
Sent: Friday, July 06, 2007 2:20 AM
To: [hidden email]
Subject: Re: Blocking access to the build

 

 

On 7/6/07, Tom Huybrechts <[hidden email]> wrote:

Just to be clear: 'Enable security' is a checkbox in the configuration
page which enables what you describe.

Tom


Lol ...the power of semantics :) .Thanks
--

"Don't take the name of root in vain."

Jeff  Mutonho
Cape Town
South Africa

GoogleTalk : ejbengine
Skype        : ejbengine
Registered Linux user number 366042

Reply | Threaded
Open this post in threaded view
|

Re: Blocking access to the build

Kohsuke Kawaguchi
Administrator
Jason Chaffee wrote:
> It would be nice if this was more granular though.  For example, there
> could be an "admin" user, a "build" user, and a "guest" user all with
> different permissions.

I hear you. This is being tracked as issue #326, I think. It's just that
I never felt the needs, so those features tend to be deferred.

One question to you: do you have existing authentication mechanism (such
as LDAP, ActiveDirectory?)

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

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

RE: Re: Blocking access to the build

tvworks
Yes, we do use LDAP and ActiveDirectory for some our authentication
needs and it would be really cool if husdon could use that, but I would
just as happy with simple solution as well.

Alternatively, it could use the user's from scm (with the ability to add
others) and they could set up their own password by clicking on their
name in the GUI and the Admin user can specify privileges on a
user-by-user basis.  

Any of the 3 solutions would work for me.  I expose most of the stuff to
the entire team, but I would like to block the admin so that someone
doesn't configure some inappropriately.

-----Original Message-----
From: Kohsuke Kawaguchi [mailto:[hidden email]]
Sent: Friday, July 06, 2007 5:33 PM
To: [hidden email]
Subject: Re: Blocking access to the build

Jason Chaffee wrote:
> It would be nice if this was more granular though.  For example, there
> could be an "admin" user, a "build" user, and a "guest" user all with
> different permissions.

I hear you. This is being tracked as issue #326, I think. It's just that

I never felt the needs, so those features tend to be deferred.

One question to you: do you have existing authentication mechanism (such

as LDAP, ActiveDirectory?)

--
Kohsuke Kawaguchi
Sun Microsystems                   [hidden email]

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

Reply | Threaded
Open this post in threaded view
|

Re: Re: Blocking access to the build

Jeff Mutonho
On 7/7/07, Jason Chaffee <[hidden email]> wrote:

> Yes, we do use LDAP and ActiveDirectory for some our authentication
> needs and it would be really cool if husdon could use that, but I would
> just as happy with simple solution as well.
>
> Alternatively, it could use the user's from scm (with the ability to add
> others) and they could set up their own password by clicking on their
> name in the GUI and the Admin user can specify privileges on a
> user-by-user basis.
>
> Any of the 3 solutions would work for me.  I expose most of the stuff to
> the entire team, but I would like to block the admin so that someone
> doesn't configure some inappropriately.
>

How does continuum do this?Using a HSQLDB?


"Don't take the name of root in vain."

Jeff  Mutonho
Cape Town
South Africa

GoogleTalk : ejbengine
Skype        : ejbengine
Registered Linux user number 366042

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