On Monday, 12 January 2015, Anders Hammar <and...@hammar.net> wrote: > Do you foresee any issues with "use all available CPU cores" when used on a > shared resource like CI server? > When writing guidelines for my customers' devs I'm always very firm on that > build jobs are not allowed to fork (or similar) freely and thereby > occupy more than their share of the resources on CI.
Much better is to use process accounting mechanisms to enforce limits. In any case, the future will be containerised builds where the build is within a Docker-style container (similar tech available for windows, just not as advanced). Containerized builds are needed to prevent drive-by hacking by pull request (may even be internal drive-by from a dev's compromised laptop etc)... That you can then apply CPU usage limits is another bonus... TL;DR we should let the OS be responsible for applying resource limits, we should use every resource we are given to the full in order to reduce the build time as that shortens the feedback loop and makes developers mire productive -S > Sure, I see the > benefit for one job to do so but it will be on the expense of all other > building jobs. > > /Anders > > On Sat, Jan 10, 2015 at 1:23 PM, Kristian Rosenvold < > kristian.rosenv...@gmail.com <javascript:;>> wrote: > > > I just released plexus-archiver version 2.10-beta-1 to maven central. > > > > This is a "technology preview" of the multithreaded Zip feature I have > > been adding to commons-compress for the last few weeks, and will > > basically use all available CPU cores when compressing the archive. > > > > To test/use this feature, you can add the following clause some plugins: > > > > <plugin> > > <groupId>org.apache.maven.plugins</groupId> > > <artifactId>maven-assembly-plugin</artifactId> > > <version>2.5.3</version> > > <dependencies> > > <dependency> > > <groupId>org.codehaus.plexus</groupId> > > <artifactId>plexus-archiver</artifactId> > > <version>2.10-beta-1</version> > > </dependency> > > <dependency> > > <groupId>org.codehaus.plexus</groupId> > > <artifactId>plexus-io</artifactId> > > <version>2.4.1</version> > > </dependency> > > </dependencies> > > </plugin> > > > > This applies to maven-war-plugin, maven-jar-plugin, maven-ear-plugin, > > maven-assembly-plugin, maven-dependency-plugin and probably a few > > others too. > > > > The feature is basically "done". commons-compress 1.10 has not yet > > been released, and the moment this happens there will be a non-beta > > version of plexus-archiver. This version contains a shaded-snapshot > > version of commons-compress. > > > > Please note that if your project basically produces a 30K jar file, > > there is not much to be expected from this upgrade. The larger your > > zip/jar/ear/war files, the more you can expect. And, of course, you > > can use this as an argument towards your boss to get a 6 core CPU. > > > > Feedback appreciated ! > > > > In other news, the java 1.6 version "3.0" was also released today, > > which contains "snappy" compression. 3.0 does not yet contain the > > parallel feature. > > > > > > Kristian > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org <javascript:;> > > For additional commands, e-mail: dev-h...@maven.apache.org > <javascript:;> > > > > > -- Sent from my phone
