Community plugins can no longer make requests to jfrog via the Orchestrator library?

SonarQube Plugin Development
1

Hi,

Recently the SonarDelphi integration tests started failing due to:

IllegalState Fail to request versions at https://repox.jfrog.io/repox/api/search/versions?g=org.sonarsource.sonarqube&a=sonar-application&remote=0&repos=sonarsource-releases&v=*

SonarDelphi uses the open-source Orchestrator library just like the official plugins
However, it looks like we’re now unable to download anything from the SonarSource artifactory.

We came across this JIRA issue which appears to be related: SONAR-21476
Making Orchestrator unusable is a pretty unfortunate change for community plugins that want to have integration tests.

How should we proceed?

Cheers,
Jonah

5 Likes
3

Hi,

Same here for our internal plugin…

Here are the changes we made to make our ITs work again. We’re running Orchestrator 4.6.0.1748.

We had to:

  1. Install the Sonar Scanner
  2. Retrieve the SonarQube distribution
  3. Replace setSonarVersion by setZipFile
File sonarScannerZipFile = new File(SONAR_SCANNER_PATH);
if (!sonarScannerZipFile.exists()) {
  try {
    FileUtils.copyURLToFile(
      new URL(SONAR_SCANNER_DOWNLOAD_LINK),
      sonarScannerZipFile
    );
  } catch (IOException e) {
    throw new IllegalStateException("Cannot download sonar-scanner", e);
  }
}
try {
  ZipUtils.unzip(sonarScannerZipFile, new File("target"));
} catch (Exception e) {
  throw new IllegalStateException("Fail to unzip sonar-scanner", e);
}
  
File sonarZipFile = new File(SONARQUBE_PATH);
if (!sonarZipFile.exists()) {
  try {
    FileUtils.copyURLToFile(
      new URL(SONARQUBE_DOWNLOAD_LINK),
      sonarZipFile
    );
  } catch (IOException e) {
    throw new IllegalStateException("Cannot download SonarQube", e);
  }
}

ORCHESTRATOR = OrchestratorExtension
  .builderEnv()
  .useDefaultAdminCredentialsForBuilds(true)
  .setZipFile(sonarZipFile)
  .build();
  
ORCHESTRATOR.start();

Hope it helps.

Same question as Jonah: Is it the proper way to proceed now?

Thank you

Regards

Nicolas

1 Like
4

Hey all @Jonah_IntegraDev and @Nicolas_Alcaraz

We’re looking into it. Sorry for the disruption. I anticipate having news for you next week!

4 Likes
6

Hello folks,

Just a heads up, we have started to work on unblocking the orchestrator, you can follow this ticket

1 Like
7

Hi Jacek,

Thanks for the heads up, and happy to hear that this is being worked on.
However, that ORCH ticket doesn’t appear to be publicly viewable like the ones in the SONAR project.

Cheers,
Jonah

8

Good afternoon, @Jonah_IntegraDev!

We have some good news: a fix has been introduced into the Orchestrator, which will require you to upgrade to the now-released 4.7.0.1861.

After that, simply override the default orchestrator.artifactory.url to central maven (or any other maven repository) and you should be good to go.

Just a side note, I cloned the sonar-delphi project and tested the changes myself; it should require minimal effort to get your tests up and running again!

Many thanks for your contribution, and I hope it all works out now.

Alain

4 Likes
10

Hi again, @Jonah_IntegraDev,

Please note that a patch has been released; you can use 4.7.1.1872 now instead.

I tried on sonar-delphi and the artifact downloads beautifully now:

image
image1529×200 41.5 KB

Good luck!

3 Likes
11

Hi @alain.kermis,

Awesome, I’m quite happy to be able to re-enable our integration tests alongside the 10.4 release. That follow-up patch was very prompt as well, much appreciated.

Thanks so much for your help with this

Jonah

1 Like
12

It is now back and working on my side. Many thanks!

1 Like
13

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.

14

I am glad to hear it. Happy coding! :slight_smile: