Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

<@U1T2STXH7> : i think i'm seeing it in pants ci as well. will look today.

oh sorry, I misread. We're on release 1.2.1, so that commit wouldn't have caused this

... i wonder if this is fallout from the travis cache wipes?

i have seen this randomly happened locally

will see if i can reproduce, didn't dig yesterday

<@U051221NF> re:inrepo pants plugins with 3rd party deps, we do:
```
[GLOBAL]
…
plugins: +[
    # Note this is effectively requirements.txt for the pants environment, so we need the deps of
    # our build dependancies, see: <https://github.com/pantsbuild/pants/issues/4001>
    "requests==2.5.3",
    “requests-futures==0.9.4”,
```

Which works and puts them in the virtualenv

Surprised that works, but I’ll take it :slightly_smiling_face:

theoretically it's the same as running the code in the `openjdk:8` docker image

<@U1T2STXH7> : those tools are bootstrapped into `~/.cache` by default... are you holding onto that run-over-run ?

(not: not the workspace: the home directory)

ok rebuilding without a cached `~/.cache` worked

i think you could also package your plugins with a setup_py target, right? and then specify them by version

then, locally, for development, just do whatever you need to do with the virtualenv

assuming you have a private python repo to upload to

the build ends up compiling the scala-interface in a single process, so it's not clear if it was a bad jar or parallel compilation was the problem

<@U1T2STXH7> : do you disable nailguns in CI?

then there are multiple processes involved

BUT, i was fairly certain that we had fixed that. certainly as of `1.2.1`.