Bugzilla – Full Text Bug Listing
| Summary: | Move PDE Sonar check to SonarCloud | ||
|---|---|---|---|
| Product: | [Eclipse Project] PDE | Reporter: | Lars Vogel <Lars.Vogel> |
| Component: | UI | Assignee: | PDE-UI-Inbox <pde-ui-inbox> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | julian.honnen, karsten.thoms, Lars.Vogel, mistria, Vikas.Chandra |
| Version: | 4.10 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Lars Vogel
Mickael, any pointer for the correct process? Do I use my personal Github user? Do I have to join an Github organization? (In reply to Lars Vogel from comment #1) > Mickael, any pointer for the correct process? Do I use my personal Github > user? Do I have to join an Github organization? For m2e, I've logged in with my personal GitHub account and created a SonarCloud "Eclipse m2e" organization which contains the project. For testing a adjusted https://ci.eclipse.org/pde/job/eclipse.pde.ui-SonarQube/ to point to a PDE UI configuration I created on https://sonarcloud.io/dashboard?id=vogellacompany_eclipse.pde.ui @Mickael, please advice if you are aware of a better process. > For m2e, I've logged in with my personal GitHub account and created a
> SonarCloud "Eclipse m2e" organization which contains the project.
Shouldn't the EF create such an organization?
> @Mickael, please advice if you are aware of a better process. I didn't check the details, but basically if you added the Maven step suggested by SonarCloud, it should work. See configuration of https://ci.eclipse.org/m2e/job/m2e-core-tests/ as example. > Shouldn't the EF create such an organization? Why adding a bottleneck when we don't need one? (In reply to Lars Vogel from comment #3) > For testing a adjusted > https://ci.eclipse.org/pde/job/eclipse.pde.ui-SonarQube/ to point to a PDE > UI configuration I created on > https://sonarcloud.io/dashboard?id=vogellacompany_eclipse.pde.ui > > @Mickael, please advice if you are aware of a better process. Mickael, I get invalid user and pw in the test build setup. Should the sonar.login key not just work. ERROR] Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.3.0.603:sonar (default-cli) on project eclipse.pde.ui: Not authorized. Please check the properties sonar.login and sonar.password. -> [Help 1] Just copying and putting as build step the exact command given by SonarCloud when.creating the project there should work. But 3.3.603 is a old version of the plugin, try a more recent one (see m2e job for that too) *** Bug 542521 has been marked as a duplicate of this bug. *** The sonar job is failing: [ERROR] Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.3.0.603:sonar (default-cli) on project eclipse.pde.ui: Not authorized. Please check the properties sonar.login and sonar.password. -> [Help 1] https://ci.eclipse.org/pde/job/eclipse.pde.ui-SonarQube/ Can you please check your credentials? No plans to work on this. |