Build Failure with SonarQube 8.9.10 Source Code: Dependency Resolution Error for `build-info-extrac

SonarQube Server / Community Build
1

Hi SonarQube Community,

I’m trying to build SonarQube 8.9.10 from the source code downloaded from the official website. However, when running ./gradlew ide, I encounter a dependency resolution error related to org.jfrog.buildinfo:build-info-extractor:2.23.0. Here’s the error snippet:

FAILURE: Build failed with an exception.  

* What went wrong:  
A problem occurred configuring root project 'sonarqube'.  
> Could not resolve all artifacts for configuration ':classpath'.  
   > Could not resolve org.jfrog.buildinfo:build-info-extractor:2.23.0.  
     ...  
     > Could not HEAD 'https://repox.jfrog.io/repox/plugins.gradle.org/.../build-info-extractor-2.23.0.pom'.  
       Received status code 401 from server

Steps I’ve already tried without success:

  1. Followed the official documentation for building from source.
  2. Verified network connectivity and permissions (no proxy/firewall issues).

My questions:

  1. Is SonarQube 8.9.10 still buildable with current dependencies?
    I suspect the JFrog repository (repox.jfrog.io) need username and password，how to get it?
  2. Does the solution in the linked apply to version 8.9?
    Can’t build SonarQube from source - #4 by ganncamp
    i follow the steps, but it doesn’t work,so I’m unsure if this is compatible with the 8.9.x branch.

Any guidance on resolving the dependency issue or confirming compatibility would be greatly appreciated. Thank you!

2

Hi,

Why? 8.9 was released almost 4 years ago. It’s 2 LTAs behind. The current version of SonarQube Community Build is 25.3. Why would you want to build something that old?

401 is a permissions error. The dependencies to build the OSS version should be publicly available, but I’m not going to pursue it internally for a version this old.

 
Ann

3

Hi Ann,

First,thanks for your reply.
The reason why I’m still using version 8.9 is that I’ve been using this version since three years ago, and it has been working well and stably.
The reason why I’m not really willing to upgrade to the latest version is that I’m worried that new problems will arise after the upgrade. :joy:

I’m going to take your advice, if this issue still blocks me.

Robert

5

Hi Ann,

I took your advice and successfully built the project using version 25.3. I will switch my service to the latest version. Thanks again for your help!
This issue has been bothering me for a full two weeks. Thank you for providing a new way of thinking that has solved my problem

Robert

1 Like