Jenkins message "Captcha required"

Esther Lansbergen August 15, 2019

We installed the parameterized builds for Jenkins on our Bitbucket (server) environment. But since  a while one of our customers do have the following problem. He use a functional account which password never expire. But he experience problems when building in "rapid fire mode" the build are fine but in one time he get's a message in Jenkins "CAPTCHA required". They checked the credential manager in Windows. Does anyone have any idea what setting can be checked to solve this problem?

Error-message in Bitbucket looks like:

2019-08-13 16:14:53,023 ERROR [threadpool:thread-1] --useraccount-- @1APRN1x974x15186049x1 esbepp --ipaddress user,--ip address bitbucket server-- "POST /scm/--project--/--repository--git/git-receive-pack HTTP/1.1" c.k.s.p.ciserver.Jenkins Exception for parametized build: Invalid password/token for user: --username-functionalaccount--


Any help is welcome. :)

2 answers

0 votes
Austin Hacker August 20, 2019

Hi @Esther Lansbergen

 

I'm the maintainer of Parameterized Builds for Jenkins. When you say that the user got the "Captcha Required" message in Jenkins do you mean the build started, tried to clone from Bitbucket and failed? If so, that would not be an issue related to the plugin as the plugin is only responsible for starting the Jenkins job, not the success of that job.

If the Jenkins job is not starting, then please open up an issue in our Github repo and provide the details asked for in the issue template as best you can.

Thank you for using our plugin and if you have any other questions, you can always use ask in our Gitter!

0 votes
Dario B
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
August 20, 2019

Hi @Esther Lansbergen ,

I might not be the best person to answer this question, anyway, the described behavior seems compatible/similar to the one described in the below Jenkins issue:

The above issue has been closed as a duplicate of the below one, that is still open and that could actually be the root-cause for this issue:

 

However, since I am not sure this is the case and/or how the add-on works, you may want to report this behavior into the Parameterized Builds for Jenkins Community at below url:

 

Finally, for more details on how the captcha works, you may also want to have a look at the following KB: How to configure CAPTCHA in Bitbucket Server

 

Have a nice day.

 

Cheers,
Dario

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events