Closed lavaman closed 9 years ago
You need to configure the user/password for every single build job in jenkins... It seems to work fine for us here... Not sure where that username is coming from...
Yeah I know. It changed even for the working jobs. Really strange. I'll let you know if I figure out why.
On Fri, Jun 5, 2015, 12:05 AM Nathan notifications@github.com wrote:
You need to configure the user/password for every single build job in jenkins... It seems to work fine for us here... Not sure where that username is coming from...
— Reply to this email directly or view it on GitHub https://github.com/nemccarthy/stash-pullrequest-builder-plugin/issues/15#issuecomment-109172401 .
So it appears there were login failures for the jenkins user in stash that triggered the captcha. When I cleared the captcha, things started working again.
So I got the plugin working, but when I added more jobs for the rest of my repos, they all started using a basic auth user of 'Atlassian Stash' instead of the user I've specified in the jobs (jenkins).