https://pantsbuild.org/ logo
Powered by
#general
  • r

    rough-minister-58256

    01/26/2016, 1:03 AM
    it could bolster our standing as a legitimate tool tho (“official apache foundation project” and all), provide added resources and help, etc etc
  • b

    bored-art-40741

    01/26/2016, 1:06 AM
    I suppose :\
  • b

    bored-art-40741

    01/26/2016, 1:07 AM
    When I hear "official apache foundation project" (spun off from some big startup), I think of thrift
  • r

    rough-minister-58256

    01/26/2016, 1:07 AM
    heh
  • r

    rough-minister-58256

    01/26/2016, 1:07 AM
    the Aurora guys seem to be getting along well w/ it
  • b

    bored-art-40741

    01/26/2016, 1:09 AM
    I seem to be the only person who doesn't feel all warm and fuzzy when I hear "Apache Project", so maybe I should entertain the notion that I'm the crazy one
  • m

    mammoth-pharmacist-54215

    01/26/2016, 1:19 AM
    I’ve never had any experience with being an Apache project, was just curious.
  • m

    mammoth-pharmacist-54215

    01/26/2016, 1:20 AM
    My previous employer tended to act as if OSS was a disease.
  • b

    bored-art-40741

    01/26/2016, 1:42 AM
  • b

    bored-art-40741

    01/26/2016, 1:42 AM
    cc @ancient-stone-50795, @jolly-chef-92794, @witty-crayon-22786, @fancy-queen-20734 and other JVM resolution stakeholders
  • b

    bored-art-40741

    01/26/2016, 1:43 AM
    This is killing our ability to get good CI in jenkins, and it's indicative of a more dangerous underlying issue
  • b

    bored-art-40741

    01/26/2016, 1:44 AM
    For now I'm going to move the entire ivy cache to be repo-local for the jenkins repo configuration
  • w

    witty-crayon-22786

    01/26/2016, 1:44 AM
    +1
  • b

    bored-art-40741

    01/26/2016, 1:44 AM
    I think this will have a non-trivial perf impact, but hopefully it will get us out of this ivy thrashing hell
  • w

    witty-crayon-22786

    01/26/2016, 1:44 AM
    that's what we do.
  • b

    bored-art-40741

    01/26/2016, 1:44 AM
    On the other hand, I really don't want this shim to become the long term "solution"
  • w

    witty-crayon-22786

    01/26/2016, 1:44 AM
    @bored-art-40741: note that most bootstrap is not concurrency safe
  • w

    witty-crayon-22786

    01/26/2016, 1:44 AM
    almost anything in ~/.cache is thus affected
  • b

    bored-art-40741

    01/26/2016, 1:44 AM
    yeah but ivy resolution isn't properly bootstrapping from the pants side of things
  • b

    bored-art-40741

    01/26/2016, 1:45 AM
    Copy code
    $ du -sh ~/.ivy2/
1.0G	/Users/pl/.ivy2
  • b

    bored-art-40741

    01/26/2016, 1:45 AM
    That's a modest ivy cache, since we don't use ivy for our actual classpath
  • b

    bored-art-40741

    01/26/2016, 1:46 AM
    Having to rebootstrap that every time we do a clean build is pretty nasty
  • b

    bored-art-40741

    01/26/2016, 1:46 AM
    If the solution is to have resolution be local but to have some sort of shim to allow local caching of just the big artifact blobs, I'm okay with that too
  • b

    bored-art-40741

    01/26/2016, 1:47 AM
    I'm less concerned about the disk usage of one-per-directory than I am with the need to hit a remote for 1G of junk frequently
  • w

    witty-crayon-22786

    01/26/2016, 1:47 AM
    @bored-art-40741: not proposing to rebootstrap for each clean build. use a unique workspace per executor
  • b

    bored-art-40741

    01/26/2016, 1:47 AM
    These are ephemeral workers
  • w

    witty-crayon-22786

    01/26/2016, 1:47 AM
    right, and there are at most N of them running at a time, right?
  • b

    bored-art-40741

    01/26/2016, 1:47 AM
    So when they come back up, it's a clean workspace
  • w

    witty-crayon-22786

    01/26/2016, 1:47 AM
    so you have /data/workspace$i
  • w

    witty-crayon-22786

    01/26/2016, 1:47 AM
    for 0-N
1...909910911...2420Latest