Hi Vivek, thanks for responding and confirming that I didn't miss anything.
I have found a workaround for my issue. I thought Blue Ocean is an entirely separate work flow from the normal pipelines, but that's not the case. Turns out, if I create the pipeline through the default Jenkins web UI, I can then use Blue Ocean to interact with this pipeline. Works for me! On Friday, April 6, 2018 at 12:54:59 AM UTC+3, vivek wrote: > > Hi Alex, > > My inlined comments: > > > I have a special "build bot" account with read-only access to our repos. > But when I log Blue Ocean in with this account, it only finds zero repos > (the bot account has none), and zero teams (or one empty default team, I > don't recall). > > Short answer, there is no bitbucket API to get repos that a user has > permission to access. There are APIs that only gives repo owned by a user > or team. > > Basically blueocean calls bitbucket API to get list of repositories for > given credentials. In this case it calls, > https://api.bitbucket.org/2.0/repositories/:[username > or team <https://api.bitbucket.org/2.0/repositories/:%5Busername%7Cteam>], > but this API only returns repos 'owned' by the user or team in context. It > doesn't return all repos across accounts that the user is has permission to > access. > > > I could specify a repo the bot has access to, but the UI doesn't let me > do that, and I can't progress. > > Right, at the moment you can only create pipelines for the repos owned by > a user or team. > > > Is there a way around this problem? > > Not unless Bitbucket provides an API that we can use to show user level > repo membership across teams/users. I guess it doesn't work for you but if > you can add 'bot account' to the team that owns this repo, that team will > appear and its repos accessible by 'bot account' can be built. > > Somewhat related, there is work in progress > https://issues.jenkins-ci.org/browse/JENKINS-46656, that will avoid users > to provide their credentials to blueocean, instead will do auth dance with > bitbucket to fetch jwt token and work with it. > > -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/bc2ef390-ab55-4b5c-9190-4fb0a32af52e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
