I am used to running mvn clean install site on my Jenkins build jobs and then 
let the Jenkins checkstyle, find bugs etc plugins display the results/trends 
over builds.

And I thought the ASF Jenkins used to have this feature.

Are there any plans to restore this?

Also, I attempted to build all of the asf maven tepid yesterday, under JDK 7, 
and some failed, e.g. Surefire needed JDK 8.

Have we moved from a minimum of JDK 7?



Sent from my iPhone

> On 30 Dec 2018, at 9:47 pm, Robert Scholte <[email protected]> wrote:
> 
>> On Sat, 29 Dec 2018 13:12:36 +0100, Hervé BOUTEMY <[email protected]> 
>> wrote:
>> 
>> Le samedi 29 décembre 2018, 11:29:53 CET Robert Scholte a écrit :
>>> I've already introduces the concept of "plans"[1][2], which also include
>>> 'site' for documentation and 'release' to verify if the project is
>>> releasable (should probably change that name to prevent confusion).
>> +1 to change the name of "release" to something like "check-release"
> 
> or release-dryRun
> 
>> 
>>> The jobs are getting more stable, so we might give it a try soon. Just
>>> need to be aware that the 'site' plan doesn't seem to work for multimodule
>>> projects yet. Better fix that first.
>> why doesn't it work? what does "don't work" mean? fail?
>> 
>> I just see "site:stage" missing to have multi-module assembled: would not
>> cause any harm for non-multi-modules
> 
> That might be the reason, I'll add that.
> 
>> 
>> additional question: once the site is build on Jenkins, can it be browsed?
> 
> I guess so.
> 
> Once INFRA-17514 is fixed I'll enable the site-plan too.
> 
> thanks,
> Robert
> 
> [1] https://issues.apache.org/jira/browse/INFRA-17514
> 
>> 
>> Regards,
>> 
>> Hervé
>> 
>>> 
>>> thanks,
>>> Robert
>>> 
>>> [1]
>>> https://gitbox.apache.org/repos/asf?p=maven-jenkins-lib.git;a=blob;f=vars/as
>>> fMavenTlpPlgnBuild.groovy;h=6502fe80819c873757e339a0f1b3186fd14303b9;hb=HEAD
>>> #l63 [2]
>>> https://gitbox.apache.org/repos/asf?p=maven-jenkins-lib.git;a=blob;f=vars/as
>>> fMavenTlpPlgnBuild.groovy;h=6502fe80819c873757e339a0f1b3186fd14303b9;hb=HEAD
>>> #l132
>>> 
>>> 
>>> On Sat, 29 Dec 2018 09:14:27 +0100, Enrico Olivelli <[email protected]>
>>> 
>>> wrote:
>>> > Hi guys,
>>> > I am trying to release Maven Assembly Plugin and I see that there are
>>> > a few showstoppers due to javadocs and site generation.
>>> > Isn't it possible to run  "javadoc:javadoc site" on CI ?
>>> >
>>> > This way we won't commit broken/unreleasable stuff
>>> >
>>> > Enrico
>>> >
>>> > ---------------------------------------------------------------------
>>> > To unsubscribe, e-mail: [email protected]
>>> > For additional commands, e-mail: [email protected]
>>> 
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [email protected]
>>> For additional commands, e-mail: [email protected]
>> 
>> 
>> 
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to