Hello all There is an ungoing discussion on [email protected] related to the difficulty to maintain the Jenkins servers running. Part of the difficulty is the large amount of resources consumed by the numerous Apache projects, some of them taking up to 10 hours to complete their build. The Apache SIS job is not yet too heavy - it takes between 15 and 45 minutes to complete on Jenkins. However the site generation consumes a very large fraction of this build time. While a "mvn clean deploy" compiles the source code only once, a "mvn clean deploy site" compiles the whole SIS project up to 18 times. We do not known why - this is a known Maven 3 issue. Maybe, in addition, there is some particularities in the SIS pom.xml.
In order to help Jenkins servers, I propose to abandon support for "mvn site" goal. All reporting configurations (Javadoc, FindBugs, etc.) would move from the <reporting> section to the <build> section in the pom.xml, in order to allow us to use the lighter "mvn javadoc:aggregate" goal instead than "mvn site". Likewise, we would use "mvn verify findbugs:findbugs" for the Findbugs report. To keep the source code simpler, I would remove most of Maven site configuration in SIS (otherwise it would be at risk to become quickly obsolete). This would increase the role of "http://sis.apache.org"; as the only SIS web site. What do peoples think? Martin
