DevOps Platform Integrations - Azure DevOps connection

SonarQube
#1

Must-share information (formatted with Markdown):

  • which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension)
  • Version 9.3 (build 51899) - Developer Edition
  • what are you trying to achieve

DevOps Platform Integrations - Azure DevOps connection

  • what have you tried so far to achieve this

  • Added our root cert to java and see that its there - we use self signed certificates

  • Verifed url and PAT token

  • Checked logs of issues

  • Checked firewalls

We have this working in 8.X LTS version and when we updated we noticed that this functions stopped working after upgrade.

image

I can see this in developer tools that it is trying to access this url [Preformatted text](https://XXXX/api/alm_settings/validate?key=adosproduktion)

image
image1628×878 65.2 KB

Azure DevOps Server integration stopped working after update to 9.4 (but analysis works)
Changing the URL of our Azure DevOps to scan with SonarQube
#2

Can this be related its in 9.4 release and we have 9.3?

[SONAR-14742] Project import from GitHub, Bitbucket and Azure can clash with existing project key - SonarSource

Release Notes - SonarSource

#3

Also this is the same Azure DevOps Server integration stopped working after update to 9.4 (but analysis works) - SonarQube - Sonar Community (sonarsource.com)

#4

Hi,

Welcome to the community!

Could this be relevant?

 
Ann

#5

We are running on Linux environment but i have verified that our root cert are installed so i dont think this is the issue.

I thinking if Sonarqube itself have some special place to look for certs - if we are updating wrong place with cert?

#6

I added certificate and verified - i really think there is a bug in Sonarqube software regarding this. I have seen so many others that have same.

#7

@mrweiland You’ve added it and it started to work?

#8

No same problem :frowning:

#9

I found this issue [SONAR-14742] Project import from GitHub, Bitbucket and Azure can clash with existing project key - SonarSource resolved in 9.4 that may have bearing on our problem - we will update and test

#10

Tested to update to 9.4 but same problem :frowning: