+1 great idea, Martin! ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: [email protected] WWW: http://sunset.usc.edu/~mattmann/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
-----Original Message----- From: Martin Desruisseaux <[email protected]> Organization: Geomatys Reply-To: "[email protected]" <[email protected]> Date: Monday, May 6, 2013 4:27 AM To: Apache SIS <[email protected]> Subject: Running "mvn clean" on Jenkins server after successful build >Hello all > >The Jenkins build on the "solaris1" node is failing since a few days >because out of disk space on that node. In order to gives Jenkins a >chance, I'm tempted to add a "mvn clean" step after successful builds. >On my local machine, disk usage after "mvn install site" is 158Mb, while >only 66Mb after clean. This is only 42% on the former disk usage. If we >verify that it doesn't impact the web site publication and the artifacts >deployment, maybe we could suggest on [email protected] to encourage >other Maven projects to do the same? > > Martin >
