Hi,

have you tried to use the jenkins-cli ? That would be the easiest
approach if you don't use authentication methods of the main stream.

I have a while ago been crunching on that issue as well and you mail
fail - as I did - if you don't use straight forward authentication but
something more exotic like TeamForge as Auth Realm.

Placing the credentials into the URL won't work afaik. But wget, curl
and another tool - whose name I can't recall right now - do have a
function that allows you to pass the credentials as parameters.
These parameters operate on different ways, depending on the tool you
use. Best approach is from curl if I ain't that wrong in
remembering ;)

That tool needs the field names to know (here j_username and
j_password) and the according parameters/credentials.
This worked fine but you have to be aware that you may need an extra
switch to set the encoding for special characters.
It's a bit of testing ...

Take care
Jan

On 2 Apr., 23:43, Ryan Ragona <ryanrag...@gmail.com> wrote:
> Minor update: I would be totally fine making a 'builder' user with read
> access and then just authenticating in the URL, something like:
>
> wget http://username:passw...@host.com:8080/job/test/build?token=build
>
> ... but that doesn't appear to work. That solution seems so close to what I
> want; does anyone see something blatantly incorrect with the
> username:password credentials passed in the URL like that? My main goal
> here is just to get builds triggering without allowing any random person to
> read my Jenkins stuff.
>
>
>
>
>
>
>
> On Mon, Apr 2, 2012 at 2:26 PM, Anogar <ryanrag...@gmail.com> wrote:
> > Is there a way to allow anonymous users to trigger builds but NOT view
> > the project? I just want something like the following to work:
>
> > wgethttp://host.com:8080/job/test/build?token=build
>
> > ... and it works just fine as long as the "Anonymous" user has
> > permissions for both overall/read and job/read. Is there a way to make
> > it so that all anonymous users see is the login box but remote
> > services can still trigger builds?

Reply via email to