Launch tests and Sonar analysis.<BR/>
This job is also impacted by Sirius tests problem on Eclipse infrastructure (see bugzilla <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=445371">445371</a> for more details).<BR/>
The Eclipse infrastructure has moved from SonarQube to SonarCloud (see bugzilla <a href="https://bugs.eclipse.org/bugs/show_bug.cgi?id=553734#c3">553734</a>). So results of the analyzes launched before december 2019 are available on <a href="https://sonar.eclipse.org/dashboard/index/org.eclipse.sirius:sirius-parent">SonarQube</a> and the other launched after are available on <a href="https://sonarcloud.io/dashboard?id=org.eclipse.sirius">SonarCloud</a>.<BR/>
"swtbot" profile has been removed since december 2019. The Eclipse platform changes, JIPP and/or Container Docker, make swtbot fail with unknown reasons (maybe resources problem on Docker). To reactivate it, just add "swtbot" to the profiles list in the 2 maven commands.<BR/>
<BR/>
In february 2024, some changes have been done to "reenable" Sonar code coverage. Swtbot tests have been added again (probably OK because of the new pod with 6Go instead of 4Go, see issue <a href="https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/3798">3798</a>). The changes in the code are visible in Github. Concerning the configuration of this job, there are two steps:<BR>
<UL>
  <LI>A first mvn command to execute the tests and store the jacoco code coverage result in a binary file (same for all tests suite).</LI>
  <LI>A second mvn command to consume the previous result to generate one result XML file per module, that is used just after by Sonar.</LI>
</UL>