Example configuration for the isolated strategy.

Review Request #2185 - Created May 9, 2015 and submitted

Information
Stu Hood
pants
16b682a...
Reviewers
pants-reviews
benjyw, fkorotkov, jsirois, zundel
  • Example configuration for the isolated strategy.

This is approximately the configuration we use with the isolated strategy and zinc for java. We may not want to actually commit this upstream, but it might be useful to have for posterity.

The last missing piece of our effort was a quick one-off Task that jars classpath entries that match a particular regex. This was necessary because as discussed previously, giving the JVM 1100 input directories (900 targets + 200 resource targets) did not work out terribly well. We'll be working to upstream better solutions to that problem soon.


  

Issues

  • 0
  • 3
  • 0
  • 3
Description From Last Updated
Benjy Weinberger
Eric Ayers
Stu Hood
Stu Hood
Review request changed

Status: Closed (submitted)

Eric Ayers

   
pants.ini.isolated (Diff revision 2)
 
 

If we are to use this config file in ci tests, do we want this configured or will it matter? I guess it won't really be a cached dir unless we configure it in travis-ci.

As an aside, I've never understood the purpose of a local artifact cache. How is this different from what's already stored under buildroot? I still get occasions when users need to run ./pants clean-all and am concerned that adding another layer of caching like this is going to make getting users back to a sane state by cleaning up more difficult.

Loading...