# Report with key 'com.sonarsource.sonarqube' has not yet been created

**URL:** <https://community.sonarsource.com/t/report-with-key-com-sonarsource-sonarqube-has-not-yet-been-created/62414>\
**Category:** SonarQube Server / Community Build\
**Tags:** teamcity, bitbucket, sonarqube\
**Created:** [April 29, 2022, 9:39am UTC](https://community.sonarsource.com/t/report-with-key-com-sonarsource-sonarqube-has-not-yet-been-created/62414 "2022-04-29T09:39:25Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![samwise](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/samwise/32/33250_2.png) [@samwise](https://community.sonarsource.com/u/samwise)\
**Post date:** [April 29, 2022, 9:39am UTC](https://community.sonarsource.com/t/report-with-key-com-sonarsource-sonarqube-has-not-yet-been-created/62414/1 "2022-04-29T09:39:25Z")

</div>

**Versions using:**

- SonarQube Developer Edition Version 8.9.6 (build 50800)
- BitBicket Server 7.17
- TeamCity Enterprise 2021.1.4

**What are you trying to achieve:**  
Trying to get pull request decoration working.

**What have you tried so far to achieve this:**

1. Added SonarQube report in Code Insights settings in BitBucket  

2. PR build triggers in TeamCity upon opening PR in BitBicket

3. PR build in TeamCity triggers SonarQube build.

4. SonarQube build finishes successfully, but the status of the build is apparently not communicated back to BitBicket.

5. Have set Pull Request Decoration settings in SonarQube to point to our BitBucket instance too.  

**What is not working:**  
The SonarQube build status is not sent back to BitBucket apparently.

![bb-sq-2](https://europe1.discourse-cdn.com/sonarsource/uploads/sonarcommunity/original/3X/4/2/424a7e2e9c64eeb5eeae4334577bef801013f1f3.png)

Any help is greatly appreciated.

---

<div class="post-metadata">

**Author:** ![Colin](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/colin/32/55255_2.png) [@Colin](https://community.sonarsource.com/u/Colin)\
**Post date:** [May 2, 2022, 7:16am UTC](https://community.sonarsource.com/t/report-with-key-com-sonarsource-sonarqube-has-not-yet-been-created/62414/2 "2022-05-02T07:16:19Z")

</div>

Hey there.

In SonarQube, are there any warnings on the PR analysis?

 ![Screenshot 2022-05-02 at 09.15.51](https://europe1.discourse-cdn.com/sonarsource/uploads/sonarcommunity/original/3X/3/f/3f80dd753f8c4cdf7cb9eed0a9f619b2d9a2c4ec.jpeg)

---

<div class="post-metadata">

**Author:** ![samwise](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/samwise/32/33250_2.png) [@samwise](https://community.sonarsource.com/u/samwise)\
**Post date:** [May 6, 2022, 12:23pm UTC](https://community.sonarsource.com/t/report-with-key-com-sonarsource-sonarqube-has-not-yet-been-created/62414/3 "2022-05-06T12:23:55Z")

</div>

Hi, thanks for the tip. There was indeed a warning that said “…failed to access BitBucket Server…”. The issue turned out to be because the personal access token added to SonarQube didn’t have access to the repository in BitBucket. Solved the problem by adding the necessary access.

Thank you.

---

<div class="post-metadata">

**Author:** ![Jin\_Wang](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/jin_wang/32/41890_2.png) [@Jin\_Wang](https://community.sonarsource.com/u/Jin_Wang)\
**Post date:** [February 9, 2023, 12:35am UTC](https://community.sonarsource.com/t/report-with-key-com-sonarsource-sonarqube-has-not-yet-been-created/62414/4 "2023-02-09T00:35:50Z")

</div>

I bumped into this issue also. Can you share the process of adding necessary access for the personal token? Thanks

---

<div class="post-metadata">

**Author:** ![DaBrownBergkamp](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/dabrownbergkamp/32/43543_2.png) [@DaBrownBergkamp](https://community.sonarsource.com/u/DaBrownBergkamp)\
**Post date:** [March 27, 2023, 5:15pm UTC](https://community.sonarsource.com/t/report-with-key-com-sonarsource-sonarqube-has-not-yet-been-created/62414/5 "2023-03-27T17:15:59Z")

</div>

I bumped into a similar issue. I checked SonarQube to see if there were any warnings. I did encounter one warning.  
 ![image (22)](https://europe1.discourse-cdn.com/sonarsource/uploads/sonarcommunity/original/3X/4/7/47c606fb455509103b1be6789c29f7ed97fb94f6.png)  
 ![image (23)](https://europe1.discourse-cdn.com/sonarsource/uploads/sonarcommunity/original/3X/1/f/1ff3ca2e0b55cc83bcf2411cd994f0e5b0a1da7a.png)  
I updated the sonar analysis (in my jenkins job) with the appropriate path for the sonar.java.libraries property and it worked.  
However, the larger issue still exists.  
 ![image](https://europe1.discourse-cdn.com/sonarsource/uploads/sonarcommunity/original/3X/6/f/6f4814242630b7fe195b45339e8974327ca24c39.png)  
May I know where the report with key ‘com.sonarsource.sonarqube’ is located ?

---

<div class="post-metadata">

**Author:** ![samwise](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/samwise/32/33250_2.png) [@samwise](https://community.sonarsource.com/u/samwise)\
**Post date:** [March 27, 2023, 5:48pm UTC](https://community.sonarsource.com/t/report-with-key-com-sonarsource-sonarqube-has-not-yet-been-created/62414/6 "2023-03-27T17:48:34Z")

</div>

Hi, perhaps go to Project Settings in SonarQube and see if the BitBucket server (or another git server) info and project info are specified there.  
 ![image](https://europe1.discourse-cdn.com/sonarsource/uploads/sonarcommunity/original/3X/6/f/6f490197e06a01b0ea1800f9931ff26a8df7a34c.png)

 ![image](https://europe1.discourse-cdn.com/sonarsource/uploads/sonarcommunity/original/3X/1/7/1788c6fa37f553fe0ee83abdc0b0df06b17f995f.png)

---

<div class="post-metadata">

**Author:** ![DaBrownBergkamp](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/dabrownbergkamp/32/43543_2.png) [@DaBrownBergkamp](https://community.sonarsource.com/u/DaBrownBergkamp)\
**Post date:** [March 27, 2023, 6:01pm UTC](https://community.sonarsource.com/t/report-with-key-com-sonarsource-sonarqube-has-not-yet-been-created/62414/7 "2023-03-27T18:01:42Z")

</div>

Hello samwise ,  
I don’t have a PR Decoration tab.

 ![image](https://europe1.discourse-cdn.com/sonarsource/uploads/sonarcommunity/original/3X/3/d/3d427c19a13cc8f7311615c47d1b382d1f4fe6de.png)

I configured the BitBucket Server, Project Key, Repo Slug in the DevOps Platform Integrations tab

 ![image](https://europe1.discourse-cdn.com/sonarsource/uploads/sonarcommunity/original/3X/8/7/875b6452d0f1d1b8a53cef657deec34e15ad354f.jpeg)

---

<div class="post-metadata">

**Author:** ![mangomam](https://avatars.discourse-cdn.com/v4/letter/m/0ea827/32.png) [@mangomam](https://community.sonarsource.com/u/mangomam)\
**Post date:** [January 30, 2024, 10:42am UTC](https://community.sonarsource.com/t/report-with-key-com-sonarsource-sonarqube-has-not-yet-been-created/62414/8 "2024-01-30T10:42:18Z")

</div>

Following can see in PR analysis

- Pull request decoration didnt happen. Failed to access bitbucket server, the repository or the pull request
- Dependencies/libraries were not provided for analysis of Source files. The ‘sonar.java.libraries’ property is empty. Verify your configuration, as you might end up with less precise results.

---

<div class="post-metadata">

**Author:** ![mangomam](https://avatars.discourse-cdn.com/v4/letter/m/0ea827/32.png) [@mangomam](https://community.sonarsource.com/u/mangomam)\
**Post date:** [January 30, 2024, 11:02am UTC](https://community.sonarsource.com/t/report-with-key-com-sonarsource-sonarqube-has-not-yet-been-created/62414/9 "2024-01-30T11:02:31Z")

</div>

can someone advise to fix the following PR analysis

- Pull request decoration didnt happen. Failed to access bitbucket server, the repository or the pull request
- Dependencies/libraries were not provided for analysis of Source files. The ‘sonar.java.libraries’ property is empty. Verify your configuration, as you might end up with less precise results.
