17 May
2018
17 May
'18
10:01 p.m.
Hi devs,
Context:
* I lost the config on ci.xwiki.org to push maven results to sonar.xwiki.org. I can find
them back for sure but will take me a bit of time.
* We don’t use sonar.xwiki.org that much
* We now have https://sonarcloud.io/organizations/xwiki/projects to which we can push
results from our builds
* https://sonarcloud.io/organizations/xwiki/projects is always up to date in term of sonar
version and we don’t need to maintain it
So my proposal is to decommission sonar.xwiki.org and to configure
https://sonarcloud.io/organizations/xwiki/projects the way we want (I already did that a
bit but we can tune it more) and modify our maven build to push to it.
WDYT?
Thanks
-Vincent
17 May
17 May
11 p.m.
Hi,
On 05/17/2018 10:01 PM, Vincent Massol wrote:
Hi devs,
Context:
* I lost the config on ci.xwiki.org to push maven results to sonar.xwiki.org. I can find
them back for sure but will take me a bit of time.
* We don’t use sonar.xwiki.org that much
* We now have https://sonarcloud.io/organizations/xwiki/projects to which we can push
results from our builds
* https://sonarcloud.io/organizations/xwiki/projects is always up to date in term of
sonar version and we don’t need to maintain it
So my proposal is to decommission sonar.xwiki.org and to configure
https://sonarcloud.io/organizations/xwiki/projects the way we want (I already did that a
bit but we can tune it more) and modify our maven build to push to it.
WDYT?
+1 for the general idea as it makes one a platform less to worry about.
I see that sonarcloud.io is free for OSS projects, then it would also be
interesting to add some of the most important contrib projects
(recommended, bundled by default, …) that we have.
Thanks,
Clément
Thanks
-Vincent
18 May
18 May
9:16 a.m.
Sure, but we need to add platform to it too.
Still it's a pity to loose all the work done during the last GCI
regarding false positives.
On Thu, May 17, 2018 at 10:01 PM, Vincent Massol <vincent(a)massol.net> wrote:
Hi devs,
Context:
* I lost the config on ci.xwiki.org to push maven results to sonar.xwiki.org. I can find
them back for sure but will take me a bit of time.
* We don’t use sonar.xwiki.org that much
* We now have https://sonarcloud.io/organizations/xwiki/projects to which we can push
results from our builds
* https://sonarcloud.io/organizations/xwiki/projects is always up to date in term of
sonar version and we don’t need to maintain it
So my proposal is to decommission sonar.xwiki.org and to configure
https://sonarcloud.io/organizations/xwiki/projects the way we want (I already did that a
bit but we can tune it more) and modify our maven build to push to it.
WDYT?
Thanks
-Vincent
--
Thomas Mortagne
9:31 a.m.
On 18 May 2018, at 09:16, Thomas Mortagne
<thomas.mortagne(a)xwiki.com> wrote:
Sure, but we need to add platform to it too.
Still it's a pity to loose all the work done during the last GCI
regarding false positives.
I think it doesn’t matter because on sonarcloud we use the default sonar rules which they
have tuned to be good and the classification is completely different anyway.
Thanks
-Vincent
On Thu, May 17, 2018 at 10:01 PM, Vincent Massol <vincent(a)massol.net> wrote:
Hi devs,
Context:
* I lost the config on ci.xwiki.org to push maven results to sonar.xwiki.org. I can find
them back for sure but will take me a bit of time.
* We don’t use sonar.xwiki.org that much
* We now have https://sonarcloud.io/organizations/xwiki/projects to which we can push
results from our builds
* https://sonarcloud.io/organizations/xwiki/projects is always up to date in term of
sonar version and we don’t need to maintain it
So my proposal is to decommission sonar.xwiki.org and to configure
https://sonarcloud.io/organizations/xwiki/projects the way we want (I already did that a
bit but we can tune it more) and modify our maven build to push to it.
WDYT?
Thanks
-Vincent
--
Thomas Mortagne 
22 May
22 May
12:31 p.m.
Hi,
On Fri, May 18, 2018 at 10:16 AM, Thomas Mortagne <thomas.mortagne(a)xwiki.com
wrote:
Sure, but we need to add platform to it too.
Still it's a pity to loose all the work done during the last GCI
regarding false positives.
Any chance we could export those comments and maybe at least have a list of
the Confirmed false positives to compare them with their current status on
sonarcloud.io and see if they are still relevant or not?
Otherwise +1, for the same reasons expressed by Clement.
Thanks,
Eduard
>
> On Thu, May 17, 2018 at 10:01 PM, Vincent Massol <vincent(a)massol.net>
wrote:
> > Hi devs,
> >
> > Context:
> > * I lost the config on ci.xwiki.org to push maven results to
> sonar.xwiki.org. I can find them back for sure but will take me a bit of
> time.
> > * We don’t use sonar.xwiki.org that much
> > * We now have https://sonarcloud.io/organizations/xwiki/projects to
> which we can push results from our builds
> > * https://sonarcloud.io/organizations/xwiki/projects is always up to
> date in term of sonar version and we don’t need to maintain it
> >
> > So my proposal is to decommission sonar.xwiki.org and to configure
> https://sonarcloud.io/organizations/xwiki/projects the way we want (I
> already did that a bit but we can tune it more) and modify our maven build
> to push to it.
> >
> > WDYT?
> >
> > Thanks
> > -Vincent
> >
>
>
>
> --
> Thomas Mortagne
>
12:33 p.m.
On 22 May 2018, at 12:31, Eduard Moraru
<enygma2002(a)gmail.com
Not that I know of.
Thanks
-Vincent
wrote:
Hi,
On Fri, May 18, 2018 at 10:16 AM, Thomas Mortagne <thomas.mortagne(a)xwiki.com
wrote:
Sure, but we need to add platform to it too.
Still it's a pity to loose all the work done during the last GCI
regarding false positives.
Any chance we could export those comments and maybe at least have a list of
the Confirmed false positives to compare them with their current status on
sonarcloud.io and see if they are still relevant or not?
Otherwise +1, for the same reasons expressed by Clement.
Thanks,
Eduard
>
> On Thu, May 17, 2018 at 10:01 PM, Vincent Massol <vincent(a)massol.net>
> wrote:
>> Hi devs,
>>
>> Context:
>> * I lost the config on ci.xwiki.org to push maven results to
> sonar.xwiki.org. I can find them back for sure but will take me a bit of
> time.
>> * We don’t use sonar.xwiki.org that much
>> * We now have https://sonarcloud.io/organizations/xwiki/projects to
> which we can push results from our builds
>> * https://sonarcloud.io/organizations/xwiki/projects is always up to
> date in term of sonar version and we don’t need to maintain it
>>
>> So my proposal is to decommission sonar.xwiki.org and to configure
> https://sonarcloud.io/organizations/xwiki/projects the way we want (I
> already did that a bit but we can tune it more) and modify our maven build
> to push to it.
>>
>> WDYT?
>>
>> Thanks
>> -Vincent
>>
>
>
>
> --
> Thomas Mortagne
>
18 May
18 May
11:29 a.m.
+0
Thanks,
Marius
On Thu, May 17, 2018 at 11:01 PM, Vincent Massol <vincent(a)massol.net> wrote:
Hi devs,
Context:
* I lost the config on ci.xwiki.org to push maven results to
sonar.xwiki.org. I can find them back for sure but will take me a bit of
time.
* We don’t use sonar.xwiki.org that much
* We now have https://sonarcloud.io/organizations/xwiki/projects to which
we can push results from our builds
* https://sonarcloud.io/organizations/xwiki/projects is always up to date
in term of sonar version and we don’t need to maintain it
So my proposal is to decommission sonar.xwiki.org and to configure
https://sonarcloud.io/organizations/xwiki/projects the way we want (I
already did that a bit but we can tune it more) and modify our maven build
to push to it.
WDYT?
Thanks
-Vincent
6:48 p.m.
+0
Thanks,
Caty
On Fri, May 18, 2018 at 11:29 AM, Marius Dumitru Florea <
mariusdumitru.florea(a)xwiki.com> wrote:
+0
Thanks,
Marius
On Thu, May 17, 2018 at 11:01 PM, Vincent Massol <vincent(a)massol.net>
wrote:
Hi devs,
Context:
* I lost the config on ci.xwiki.org to push maven results to
sonar.xwiki.org. I can find them back for sure but will take me a bit of
time.
* We don’t use sonar.xwiki.org that much
* We now have https://sonarcloud.io/organizations/xwiki/projects to
which
we can push results from our builds
* https://sonarcloud.io/organizations/xwiki/projects is always up to
date
in term of sonar version and we don’t need to
maintain it
So my proposal is to decommission sonar.xwiki.org and to configure
https://sonarcloud.io/organizations/xwiki/projects the way we want (I
already did that a bit but we can tune it more) and modify our maven
build
to push to it.
WDYT?
Thanks
-Vincent
6 Jan
6 Jan
1:37 p.m.
Hi devs,
I’ve now progressed on this over the weekend.
* I’ve configured ci.xwiki.org to define a ’sonar’ config that points to sonarcloud.io
* I’ve modified our top level pom in commons to use the proper sonarqube plugin (we were
using a too old version for sonarcloud)
* I’ve modified and integrated our main jenkins pipeline to add a parameter
“sonar=true|false” to deploy to the ’sonar’ config.
* I’ve modified the Jenkinsfile of commons, rendering & platform so that the ‘quality’
build deploys the results to sonarcloud.io. This is the best part since it’s now
integrated in our pipeline and we don’t need the 4 specific jenkins jobs for sonar that we
have. FTM I’ve disabled them, but my plan is to remove them completely next week after I
verify that it all works fine.
* Bonus: we now have SonarQube results displayed on the jenkins page. For ex, see
https://ci.xwiki.org/view/Recommended%20Builds/job/XWiki/job/xwiki-commons/…
Build speed consequences:
* I think this makes use loose 3mn on the commons build, see
https://ci.xwiki.org/view/Recommended%20Builds/job/XWiki/job/xwiki-commons/….
Build #512 is the one that ran sonar:sonar and deployed to sonarcloud.io.
* I’m waiting for the rendering and platform builds to see how much time more it takes
there.
Next steps:
* Tune the rules on sonarcloud.io and define a strategy to use it
* Later on, decide if we want to break the CI job on some rules (quality gate)
* Tune the sonarqube config in our poms so that we get correct jacoco coverage (right now
it doesn’t seem correct and probably doesn’t include integration testing). I’m working on
this one ATM.
* Continue investigating the usage of
https://github.com/jenkinsci/parameterized-scheduler-plugin to be able to have scheduled
triggers inside our main pipeline to run some parts of the build only at certain times
(like being able to run the sonar part only once every day for ex if that’s what we want).
We could also imagine running it only once out of 3 builds for example (easier to do I
think).
Thanks
-Vincent
On 17 May 2018, at 22:01, Vincent Massol
<vincent(a)massol.net> wrote:
Hi devs,
Context:
* I lost the config on ci.xwiki.org to push maven results to sonar.xwiki.org. I can find
them back for sure but will take me a bit of time.
* We don’t use sonar.xwiki.org that much
* We now have https://sonarcloud.io/organizations/xwiki/projects to which we can push
results from our builds
* https://sonarcloud.io/organizations/xwiki/projects is always up to date in term of
sonar version and we don’t need to maintain it
So my proposal is to decommission sonar.xwiki.org and to configure
https://sonarcloud.io/organizations/xwiki/projects the way we want (I already did that a
bit but we can tune it more) and modify our maven build to push to it.
WDYT?
Thanks
-Vincent
7 Jan
7 Jan
10:06 a.m.
Hi devs,
On 6 Jan 2019, at 13:37, Vincent Massol
<vincent(a)massol.net> wrote:
[snip]
Build speed consequences:
* I think this makes use loose 3mn on the commons build, see
https://ci.xwiki.org/view/Recommended%20Builds/job/XWiki/job/xwiki-commons/….
Build #512 is the one that ran sonar:sonar and deployed to sonarcloud.io.
* I’m waiting for the rendering and platform builds to see how much time more it takes
there.
Good news, I’ve checked rendering and there’s no speed impact in the build even though
it’s now deploying to sonarcloud.io, see
https://ci.xwiki.org/view/Recommended%20Builds/job/XWiki/job/xwiki-renderin…
:)
Thanks
-Vincent
[snip]
2123
days inactive
2358
days old
9 comments
6 participants
participants (6)
-
Clément Aubin -
Ecaterina Moraru (Valica) -
Eduard Moraru -
Marius Dumitru Florea -
Thomas Mortagne -
Vincent Massol