Right now Bitbucket Source plugin requires putting personal password to be able to monitor branches. This is a security risk to expose such information. The proper way would be to create an OAuth consumer on Bitbucket side, set proper access permissions and use OAuth key+secret to authenticate to Bitbucket.
Is it true that OAuth does not work at the moment? I have been trying to use them in the credentials but i keep getting:
Started
Consulting Bitbucket Team/Project
Connecting to https://bitbucket.org using xxxxxxx/****** (Credentials Name)
FATAL: Failed to recompute children of my-project
com.cloudbees.jenkins.plugins.bitbucket.api.BitbucketRequestException: HTTP request error. Status: 401: UNAUTHORIZED.
at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.getRequest(BitbucketCloudApiClient.java:416)
at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.getTeam(BitbucketCloudApiClient.java:328)
at com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMNavigator.visitSources(BitbucketSCMNavigator.java:164)
at jenkins.branch.OrganizationFolder.computeChildren(OrganizationFolder.java:125)
at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:154)
at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:122)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:410)
Finished: FAILURE
Is it true that this does not work at the moment? I have been trying to use OAuth credentials an i just get:
Started
Consulting Bitbucket Team/Project
Connecting to https://bitbucket.org using xxxx/****** (xxxxx)
FATAL: Failed to recompute children of my-job
com.cloudbees.jenkins.plugins.bitbucket.api.BitbucketRequestException: HTTP request error. Status: 401: UNAUTHORIZED.
at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.getRequest(BitbucketCloudApiClient.java:416)
at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.getTeam(BitbucketCloudApiClient.java:328)
at com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMNavigator.visitSources(BitbucketSCMNavigator.java:164)
at jenkins.branch.OrganizationFolder.computeChildren(OrganizationFolder.java:125)
at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:154)
at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:122)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:410)
Finished: FAILURE
Is it true that this does not work at the moment? I have been trying to use OAuth credentials an i just get:
{code}
Started Consulting Bitbucket Team/Project Connecting to https://bitbucket.org using xxxx/****** (xxxxx) FATAL: Failed to recompute children of my-job com.cloudbees.jenkins.plugins.bitbucket.api.BitbucketRequestException: HTTP request error. Status: 401: UNAUTHORIZED.
at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.getRequest(BitbucketCloudApiClient.java:416) at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.getTeam(BitbucketCloudApiClient.java:328) at com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMNavigator.visitSources(BitbucketSCMNavigator.java:164) at jenkins.branch.OrganizationFolder.computeChildren(OrganizationFolder.java:125) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:154) at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:122) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) Finished: FAILURE
Would it be possible to increase the prority of this issue? Our company will not allow it's use unless we can use secure authentication methods, and this plugin looks great and just what we need.
Sorry to be persistent , is there any news about this? We would very much like to be able to use this plugin. Is there any way we can help? Unfortunately we are do not have experience in jenkins development (only usage), but we are happy to contribute where possible.
At the least, could you update the landing page for this plugin to reflect the fact that it doesn't support OAuth? I worked on this for a long time before finding this ticket. As far as the Jenkins credentials page is concerned, OAuth credentials are the same as other username/password. Putting this in the README would help a lot. Thanks.