Does it mean that combinations of Maven and JDK reached the disk limit? I am using JDK 7, 8, 11, 12 and Maven 3.2, 3.3 and 3.5. So 12 combinations altogether. Each makes cleanup, and the archiver stores totally 240 Mega Bytes per build. We have 10 surefire builds which makes 2.4 GB per Linux. Windows is a bit smaller. If I could remove JDK 12, we would save only 25% on the disk. Sometimes the archived ZIP files are investigated and often a lost connection is found.
T On Tue, Dec 25, 2018 at 8:38 PM Robert Scholte <[email protected]> wrote: > Java 9 and 10 have the same status as Java 1.7 right now. > Knowing that the majority of Java projects/developers will go from 1.8 to > 11 (because this is in the first LTS for some vendors) it probably makes > sense to drop these versions by default. > I'll remove them. > > Robert > > On Tue, 25 Dec 2018 19:16:11 +0100, Michael Osipov <[email protected]> > wrote: > > > Friends, > > > > can someone drop those version from the Jenkins config? They aren't > > supported anymore and were short term releases anyway. > > > > Michael > > > > --------------------------------------------------------------------- > > 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] > >
