We use Apache to proxy to the port number, so something like
https://ci.company.com/job/my_job/build... etc. If I hit the same URL
while logged in, it works just fine.
Nick
On Thu, Apr 25, 2013 at 12:08 PM, Eric Pyle wrote:
> What is the URL you are hitting when you try to run the job? Somet
What is the URL you are hitting when you try to run the job? Something
like http://jenkins.company.com:8080/jenkins/job/my_job/build ? Or are
you using CLI?
Eric
On 4/25/2013 10:02 AM, Nick Walke wrote:
These are the permissions I have set http://i.imgur.com/SveO50h.png.
They seem sane for a
These are the permissions I have set http://i.imgur.com/SveO50h.png. They
seem sane for an anonymous user, but when external scripts hit the API,
they are given a 403.
Nick
On Thu, Apr 25, 2013 at 8:40 AM, Eric Pyle wrote:
> I would think if you remove Overall Read permission for anonymous,
I would think if you remove Overall Read permission for anonymous, as
well as most other permissions, that would do it.
Eric
On 4/25/2013 9:29 AM, Nick Walke wrote:
Anybody able to help out with this?
On Wednesday, April 24, 2013 11:16:15 AM UTC-5, Nick Walke wrote:
Hello! Basically wha
Anybody able to help out with this?
On Wednesday, April 24, 2013 11:16:15 AM UTC-5, Nick Walke wrote:
>
> Hello! Basically what the subject says, I want an external service
> (BitBucket in this case) to be able to build jobs, but I also want to lock
> down Jenkins so that anonymous can't view j
Hello! Basically what the subject says, I want an external service
(BitBucket in this case) to be able to build jobs, but I also want to lock
down Jenkins so that anonymous can't view jobs/code. I've tried giving
anonymous the build attribute, but that doesn't seem to help anything. Is
there
