-
Bug
-
Resolution: Unresolved
-
Blocker
-
None
-
jenkins/jenkins lts docker image
Trying to create a new pipeline with bitbucket cloud, when I enter my credentials I get an error 'invalid username / password'. I am 100% sure my credentials are OK. I can use them without a problem logging into bitbucket cloud directly.
I also tried to create an app password, giving it full control of anything. That gives the same error.
github works fine, but I really need to use bitbucket in this case . Again, from www.bitbucket.org I can login fine with my email address as username and typing in the exact same password.
Anything I am doing wrong?
PS: created an issue in the wrong issue tracker, here is the link for the screenshot anyway
[JENKINS-68948] create pipeline bitbucket cloud - Invalid username and/or password
Description |
Original:
Trying to create a new pipeline with bitbucket cloud, when I enter my credentials I get an error 'invalid username / password'. I am 100% sure my credentials are OK. I can use them without a problem logging into bitbucket cloud directly.
I also tried to create an app password, giving it full control of anything. That gives the same error. Anything I am doing wrong? PS: created an issue in the wrong issue tracker, here is the link for the screenshot anyway https://github.com/jenkins-infra/jenkins.io/issues/5281 |
New:
Trying to create a new pipeline with bitbucket cloud, when I enter my credentials I get an error 'invalid username / password'. I am 100% sure my credentials are OK. I can use them without a problem logging into bitbucket cloud directly.
I also tried to create an app password, giving it full control of anything. That gives the same error. github works fine, but I really need to use bitbucket in this case :). Again, from [www.bitbucket.org|http://www.bitbucket.org/] I can login fine with my email address as username and typing in the exact same password. Anything I am doing wrong? PS: created an issue in the wrong issue tracker, here is the link for the screenshot anyway [https://github.com/jenkins-infra/jenkins.io/issues/5281] |