For use with a multibranch type job you'll need username & password/token
credentials for a Bitbucket user which has read access to the repo (or
admin access if you want Jenkins to setup the hooks automatically).
For use with an organisation folder type job (with Bitbucket server at
least - haven't used Bitbucket cloud so can't fully comment) you'll want a
username & password/token credentials for a Bitbucket user which has read
access to a project (or admin access if you want Jenkins to setup the hooks
automatically).

If that's not working then you'll need to be a bit clearer about the error
that you are getting as it could be a number of things.

Richard.

On Fri, 24 Jul 2020 at 04:56, Ashish Sharma <[email protected]> wrote:

> Dear community,
>
> I need help in understanding how setting up credentials work for this
> plugin.
>
> Does this require system admin level username / password or any user
> credentials (who has read access on repo) can be provided.
>
> Also any limitations on what kind of directory that user is coming from?
> We are using delegated ldap for microsoft active directory in bitbucket.
>
> I tried to setup using a general user credentials but its not able to
> fetch repositories with project name, it keeps showing error message. Does
> this have to be the project admin user credentials?
>
> Thanks,
> Ashish
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/1fe9539e-3ee3-4e49-86d0-dfda77f3fca2o%40googlegroups.com
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAAy0hwc84N4YeCKiTO39zPDNRCdCXRpfqrjbiQxeWYPdkkCtYg%40mail.gmail.com.

Reply via email to