Can't analyze our project, because a fork has been analyzed by a different user


(Sven Hettwer) #1

Hi!

I’m currently setting up sonarcloud checks for our open source project (https://sonarcloud.io/dashboard?id=com.consol.citrus%3Acitrus), which is hosted on GitHub and build with Travis-CI

Unfortunately the check can’t be performed, because another sonar cloud user has added a fork of our project to sonarcloud.

The error message is:

Error Details
Validation of project failed:
  o Module "com.consol.citrus:citrus-arquillian" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus:citrus-jdbc" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus:citrus-http" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus:citrus-tools" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus:citrus-remote" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus:citrus-remote-maven-plugin" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus:citrus-remote-server" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus.mvn:citrus-maven" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus.mvn:citrus-maven-plugin" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus.archetypes:citrus-archetypes" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus.archetypes:citrus-quickstart-jms" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus.archetypes:citrus-quickstart-soap" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus.archetypes:citrus-quickstart" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus:citrus-test-generator" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus:citrus-docs-generator" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus:citrus-bom" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus:citrus-vertx" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus.model:citrus-model" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus.model:citrus-model-jmx" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus.model:citrus-model-kubernetes" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus.model:citrus-model-docker" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus.model:citrus-model-ssh" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus.model:citrus-model-camel" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus.model:citrus-model-jms" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus.model:citrus-model-rmi" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus.model:citrus-model-selenium" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus.model:citrus-model-ws" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus.model:citrus-model-zookeeper" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus.model:citrus-model-mail" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus.model:citrus-model-vertx" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus.model:citrus-model-ftp" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus.model:citrus-model-websocket" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus.model:citrus-model-core" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus.model:citrus-model-cucumber" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus.model:citrus-model-kafka" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus.model:citrus-model-jdbc" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus.model:citrus-model-http" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus:citrus-restdocs" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus:citrus-zookeeper" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus:citrus-cucumber" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus:citrus-kafka" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus:citrus-integration" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus:citrus-ftp" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus:citrus-java-dsl" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus:citrus-docker" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus:citrus-selenium" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus:citrus-websocket" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus:citrus-camel" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus:citrus-ws" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus:citrus-jms" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus:citrus-rmi" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus:citrus-core" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus:citrus-jmx" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus:citrus-ssh" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus:citrus-mail" is already part of project "sdenel_citrus"
  o Module "com.consol.citrus:citrus-kubernetes" is already part of project "sdenel_citrus"

Could you please help to overcome this issue? I’m looking forward to your response.

Thanks in advance and best regards,
Sven


(Sven Hettwer) #2

Hi!

I contacted the user directly. He removed his fork.
Nevertheless, I’d like to recommend a separation of namespaces so that such issues don’t come up in the future.

BR,
Sven


(Fabrice Bellingard) #3

Hi Sven,

this issue appears because you are running the analysis of your Maven project w/o explicitly specifying the project key (i.e. you rely on the Scanner for Maven to infer the project key from artifactId:groupId). If you followed the tutorial, you probably saw:

image

If you do this, then no collision would happen.


(Sven Hettwer) #4

Hi!

Thanks a lot for your response. I followed the tutorial on travis-ci.com.
I assume, I’d have to configure it as follows?

    addons:
        sonarcloud:
          organization: "citrusframework"
          projectKey: "citrus"
          token:
            secure: ************

But this is something I’d have to clarify with travis anyways because their plugin should be their scope, right?

BR,
Sven


(Fabrice Bellingard) #5

Nope, this extension is made by us. And now that I look at the documentation, I see that something is missing from the code sample that is given for Maven projects. It should be:

addons:
  sonarcloud:
    organization: "sonarcloud_organization_key"
    token:
      secure: *********
script:
  - mvn (...) sonar:sonar -Dsonar.projectKey=citrus

(Sven Hettwer) #6

Ah, okay! Thx for the info! :+1: