Thanks Aurelien, I'll try that.

On Wed, Jan 28, 2026 at 1:41 PM Aurélien Pupier <[email protected]> wrote:

> Hi,
>
> not tried recently but in the past for another project, to get the
> dashboard on local changes, I was launching a community Sonarqube instance
> <
> https://www.sonarsource.com/open-source-editions/sonarqube-community-edition/
> >
> locally and then calling the build with the coverage enabled. Usually by
> default it connects to a local instance.
>
> based on
>
> https://github.com/apache/camel/blob/bbe6a29112d6757bb1cd2df56f4371b8ce729530/Jenkinsfile#L146
> and
>
> https://github.com/apache/camel/blob/bbe6a29112d6757bb1cd2df56f4371b8ce729530/Jenkinsfile#L174
> locally this would mean to launch something like: mvn -Darchetype.test.skip
> -Dmaven.test.failure.ignore=true -Dcheckstyle.skip=true install
> -Pcoverage -Dsonar.java.experimental.batchModeSizeInKB=2048
> -Dsonar.organization=apache -Dsonar.projectKey=apache_camel
> org.sonarsource.scanner.maven:sonar-maven-plugin:sonar
>
> Regards,
>
>
>
>
> On Wed, Jan 28, 2026 at 8:17 AM Otavio Rodolfo Piske <[email protected]
> >
> wrote:
>
> > Hi Pasquale,
> >
> > Thanks for doing it. Please, is there a way to get that report locally?
> > Let's say, after running a `mvn verify` ?
> >
> > Kind regards
> >
> > On Fri, Jan 16, 2026 at 4:55 PM Pasquale Congiusti <
> > [email protected]> wrote:
> >
> > > Hi team,
> > > I've lately worked to include the code coverage metric to our Sonar
> > > dashboard [1]. From now on, we'll be tracking this metric and hopefully
> > > help increase the awareness on the quality of the code we develop. I
> > think
> > > it could be a good thing to look at from time to time to see how our
> code
> > > is evolving.
> > >
> > > Regards,
> > > Pasquale.
> > >
> > > [1] https://sonarcloud.io/summary/overall?id=apache_camel&branch=main
> > >
> >
> >
> > --
> > Otavio R. Piske
> > http://orpiske.net
> >
>


-- 
Otavio R. Piske
http://orpiske.net

Reply via email to