K - not sure what worked, but just read a script. Thanks for providing it

can I control where bundle and binary put their outputs? I'm looking at http://www.pantsbuild.org/options_reference.html#binary but nothing jumps out at me as "destination"

ah, do they all magically go to pants_distdir perhaps

Thats intended to be less magic, more default, but yeah

fair enough 🙂 just unclear to me why e.g., publish.jar has a local destination option and doesn't also go to distdir for example

because maven / sbt interop

Generally folks wanting local publish want to publish to their local m2

which is never in dist/

makes sense I guess. So almost all traditional "output" stuff goes into distdir unless there's a convention that would have it be otherwise

Yes, exactly

cool, thanks 🙂

And only dist/ if its directly consumably; otherwise "hidden" under .pants.d/...

But this is not fully uniform and has holes - jvm junit xml files for example are under .pants.d/ right now

I see

@enough-analyst-54434 wow, thanks for the quick PR on the SCM thing 🙂 it looks a lot prettier than you made it sound

is there a quick way to get

bundle

to not produce symlinks to the .pants.d folder? I can unsymlink them myself obviously

I see a symlink option under cache.bundle.jvm but that doesn't sound like what I'm talking about

Easiest is to "really" bundle.

./pants bundle.jvm --archive=zip ... && unzip dist/...

for example.

aha

Is there a way to set the amount of jvm memory used by the nailgun and zinc processes?

For zinc its:

$ ./pants options --scope=compile.zinc --name=jvm_options
compile.zinc.jvm_options = ['-Xmx4g', '-XX:MaxPermSize=512m', '-XX:+UseConcMarkSweepGC', '-XX:ParallelGCThreads=4', '-Dzinc.analysis.cache.limit=1000'] (from CONFIG)

@enough-analyst-54434 Thank you

NP. Nailguns is per-task, but these bits of pants.ini in pants itself set a default and override for one task:

$ grep -C2 jvm_options pants.ini
[DEFAULT]
# TODO: Still needed until we migrate jvm tools to subsystems.
jvm_options: ["-Xmx1g", "-XX:MaxPermSize=256m"]

local_artifact_cache: %(pants_bootstrapdir)s/artifact_cache
--

[compile.zinc]
jvm_options: [
    '-Xmx4g', '-XX:MaxPermSize=512m', '-XX:+UseConcMarkSweepGC', '-XX:ParallelGCThreads=4',
    # bigger cache size for our big projects (default is just 5)

To see all the different possible ng using options

./pants options --name=jvm_options

- though this includes jvm_options for direct java execs, not just ng calls

oic. So, the default jvm used anywhere is 1g, and then for zinc compile it’s overridden to be 4g?

In pantsbuild/pants repo only

this is straight from our dogfood

Gotcha. Thank you

does pants+ivy have some notion of "locking" dependencies? If I specify a version range (or latest) in my ivy dependencies, can pants spit out concrete versions for everything so I can reproduce that build later?

Nope