Hidden project unable to integrate

SonarQube Cloud
1

Template for a good new topic, formatted with Markdown:

  • ALM used (GitHub, Bitbucket Cloud, Azure DevOps)

Bitbucket cloud

  • CI system used (Bitbucket Cloud, Azure DevOps, Travis CI, Circle CI

Bitbucket cloud

  • Scanner command used when applicable (private details masked)

–

  • Languages of the repository
    Kotlin

  • Only if the SonarCloud project is public, the URL

    • And if you need help with pull request decoration, then the URL to the PR too

Private project

  • Error observed (wrap logs/code around with triple quotes ``` for proper formatting)
  • Steps to reproduce
  • Potential workaround

Do not share screenshots of logs – share the text itself (bonus points for being well-formatted)!

Hello!

We are using bitbucket cloud and sonar cloud reports one repository is already imported but its not showing up in either project pages ( under administration and in the project root of the organization ) is there a way to unitialize this “hidden” project and import it again? Can i do something from the bitbucket cloud side of things? Im struggling to find information on the community page that points to a fix towards this

Best Regards
Anders

2

I’ve sent you a private message for some additional details.

6

Hi @anders_akerberg,

We checked internally and the problem comes from your organization: it is currently not bound to BitBucket (nor any other platform). I don’t know how things happen but it is true that your project itself is bound.

As you just have one org and one project, the easiest here is to reset things from the beginning to have proper binding. So what you should do is:

  • Delete your project (this will cleanup the orphan binding)
  • Delete your organisation
  • Create your organisation by importing it from BitBucket
  • Import your project again

Let me know if that’s doable and fixed the situation.

Cheers,
Antoine

7

Feels very cumbersome can’t you just delete the project ? I don’t want to delete the whole organisation like that it will take alot of time to get everything sorted again as we have configured most of the repositories we want scanning on as is.

There must be something you can do here?

/Anders

8

Hello Anders,

I understand your concern. I suggested this for 2 reasons:

  • your organization was initially bound to Azure DevOps, not BitBucket
  • we could only see this single project in your organization. I don’t understand:

Are you sure that it’s on this organization? :thinking:

We won’t delete the project ourselves for security reasons, and either way, that would not solve the problem.

What you can try is to bind your Organization to BitBucket from the Organisation Settings pane. You should see this:

Screenshot 2024-05-23 at 14.54.47
Screenshot 2024-05-23 at 14.54.47710×202 16.4 KB

The you’d have to grant access from the BitBucket UI, and you should be good.

Let me know.

Antoine

9

We have already bound it

image.png
image.png2960×1262 217 KB

Currently we have 7 projects imported

image.png
image.png2764×1482 304 KB

10

Hello why is this not answered ?

11

Please respond to this

12

Hello @anders_akerberg,

I sent you a private message as it contained some sensitive information. Let’s sort this out privately and I’ll update the thread here for the community.

tl;dr;
A ghost organisation (probably an old test) is already bound to the repo, preventing the now official organization to get this binding.

13

@anders_akerberg was able to solve the problem on his own once we found who was the admin of the old organization holding the binding to this BitBucket project!

:partying_face: