Almost all our components use custom report list to build site. And also
becouse we skip tests for release build - our subpage for reports is empty.
Sylwester
pon., 4 kwi 2022, 02:32 użytkownik Tibor Digana
napisał:
> It is a nice report in Jenkins but still this cannot be compared with
>
It is a nice report in Jenkins but still this cannot be compared with Sonar.
Anyway, guys, feel free to continue in this discussion.
T
On Mon, Apr 4, 2022 at 2:26 AM Olivier Lamy wrote:
> On Mon, 4 Apr 2022 at 08:51, Tibor Digana wrote:
>
> > Regarding the next 4 reports out of 5:
> >
> > Test
On Mon, 4 Apr 2022 at 08:51, Tibor Digana wrote:
> Regarding the next 4 reports out of 5:
>
> Test report
> Checkstyle report
> PMD report and
> Taglist report
>
> we should use the Sonar Cube as a substitution and the development +
> release process should take the Sonar into account on the
Regarding the next 4 reports out of 5:
Test report
Checkstyle report
PMD report and
Taglist report
we should use the Sonar Cube as a substitution and the development +
release process should take the Sonar into account on the fly.
Then I would understand the purpose of removal.
But now I don't!
hm, I do not understand his change regarding PR #49.
The CI result is used to fail due to the Socket timeout. The same has
happened in the latest surefire result vote. The build was red, we tried to
restart the build for 3 days, and finally the build got green at the end of
the Vote.
Instead of
On Mon, 4 Apr 2022 at 06:46, Slawomir Jaranowski
wrote:
> Hi,
>
> We have plans for the next release for parents poms.
>
> Maybe I will be boring, but I still do not see any values for some of the
> reports for static documentation sites of components.
>
> Result of tests during release time has
-1
I read them sometimes
and they don't cost anything
please just ignore them if you don't use them
On 2022/04/03 20:46:19 Slawomir Jaranowski wrote:
> Hi,
>
> We have plans for the next release for parents poms.
>
> Maybe I will be boring, but I still do not see any values for some of the
>
+1
Sylwester
niedz., 3 kwi 2022, 22:46 użytkownik Slawomir Jaranowski <
s.jaranow...@gmail.com> napisał:
> Hi,
>
> We have plans for the next release for parents poms.
>
> Maybe I will be boring, but I still do not see any values for some of the
> reports for static documentation sites of
>> > > > >> > Also, I find a release mgr that does NOT check is site building
>> > > > >> beforehand
>> > > > >> > release as sloppy.
>> > > > >> >
>> > > > >> > Hence,
t;
> > > > > >> > Building everything for each commit is insane.
> > > > > >> >
> > > > > >> > Also, I find a release mgr that does NOT check is site
> building
> > > > > >> beforehand
> >
it just to suit sloppy
> > > release
> > > > >> mgrs
> > > > >> > is insane IMHO.
> > > > >> >
> > > > >> > My 5 cents.
> > > > >> >
> > > > >> > T
> > > > >>
; > > wrote:
> > > >> >
> > > >> > > Sounds good.
> > > >> > > But who has never released something and having javadoc failing
> > in
> > > >> the
> > > >> > > middle of the release or the site g
or the site generation failing once tag done
> > and
> > >> > > artifacts staged… I find this a pain
> > >> > >
> > >> > > Maybe only testing javadoc works at least ?
> > >> > >
> > >> > &g
ved
> >> > >
> >> > > On Fri, 25 Feb 2022 at 6:24 am, wrote:
> >> > >
> >> > > > and reporting profile was done for this:
> >> > > > - without reporting profile, just light site generation
> >> > &g
> >> > >
> >> > > Maybe only testing javadoc works at least ?
> >> > >
> >> > > Btw I agree some reports could be removed
> >> > >
> >> > > On Fri, 25 Feb 2022 at 6:24 am, wrote:
> >> > >
&
>> > > > - without reporting profile, just light site generation
>> > > > - with reporting profile, full documentation site
>> > > >
>> > > > disabling reporting profile for CI should do the job
>> > > >
>> > > > ---
> > and reporting profile was done for this:
> > > > - without reporting profile, just light site generation
> > > > - with reporting profile, full documentation site
> > > >
> > > > disabling reporting profile for CI should do the job
> >
> > >>
> > >> On Fri, 25 Feb 2022 at 6:24 am, wrote:
> > >>
> > >> > and reporting profile was done for this:
> > >> > - without reporting profile, just light site generation
> > >> > - with reporting profile, full docum
gt; > > disabling reporting profile for CI should do the job
> > >
> > > - Mail original -
> > > De: "herve boutemy"
> > > À: "Maven Developers List"
> > > Envoyé: Jeudi 24 Février 2022 21:21:45
> > > Objet: Re: Revi
t; > >
> > > disabling reporting profile for CI should do the job
> > >
> > > - Mail original -
> > > De: "herve boutemy"
> > > À: "Maven Developers List"
> > > Envoyé: Jeudi 24 Février 2022 21:21:45
> > >
: Jeudi 24 Février 2022 21:21:45
> >> > Objet: Re: Review of used reports for Maven project sites.
> >> >
> >> > done on GH and Jenkins, then on each commit?
> >> > we're heating oceans for nothing
> >> >
> >> > IMHO, we need to diff
t; - with reporting profile, full documentation site
>> >
>> > disabling reporting profile for CI should do the job
>> >
>> > - Mail original -
>> > De: "herve boutemy"
>> > À: "Maven Developers List"
>> > Envoyé: Jeudi
ng profile for CI should do the job
> >
> > - Mail original -
> > De: "herve boutemy"
> > À: "Maven Developers List"
> > Envoyé: Jeudi 24 Février 2022 21:21:45
> > Objet: Re: Review of used reports for Maven project sites.
> >
&g
De: "herve boutemy"
> À: "Maven Developers List"
> Envoyé: Jeudi 24 Février 2022 21:21:45
> Objet: Re: Review of used reports for Maven project sites.
>
> done on GH and Jenkins, then on each commit?
> we're heating oceans for nothing
>
> IMHO, we need to di
There is such a situation where the contributor changes the site, we vote
for his PR on GH but we lately find out that the site is broken in some
way. If I could see the site deployed to gh_pages which is a Git branch and
visualized on GH then the contributor would fix it much better.
Of course
t;
Envoyé: Jeudi 24 Février 2022 21:21:45
Objet: Re: Review of used reports for Maven project sites.
done on GH and Jenkins, then on each commit?
we're heating oceans for nothing
IMHO, we need to differentiate CI vs release documentation: CI should be much
lighter than release
- Mail original
4 Février 2022 20:53:49
Objet: Re: Review of used reports for Maven project sites.
Yes is done after release but also on jenkins for plugins and on GH builds
czw., 24 lut 2022 o 20:43 napisał(a):
> full site building with reports enabled (through reporting profile) is
> just
Yes is done after release but also on jenkins for plugins and on GH builds
czw., 24 lut 2022 o 20:43 napisał(a):
> full site building with reports enabled (through reporting profile) is
> just done after release, isn't it?
>
> - Mail original -
> De: "Slawomir Jaranowski"
> À: "Maven
full site building with reports enabled (through reporting profile) is just
done after release, isn't it?
- Mail original -
De: "Slawomir Jaranowski"
À: "Maven Developers List"
Envoyé: Jeudi 24 Février 2022 20:24:56
Objet: Review of used reports for Maven project sites.
Hi,
Building
29 matches
Mail list logo
