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

Pants

haven’t seen the teleprescence robot roll around lately

Foursquare did this well imo, they (used to) have a bigscreen feed in a lounge area in NY &amp; SF and, via sideband communication you could say - lets meet in the lounge, then do that

Yup, we have two of those now, and it's pretty much optimal

People can dial into meetings remotely and appear on the portals, or if you're just SF + NY then they're just always there

It feels much more like the offices are connected via wormholes and less like hooking into some crazy telepresence system

I' telecommuted for 10 years of my life and the voice/vid systems all were alienating in the end - worse than just not having them imo

yeah, we’ve switched 100% to google hangouts and it’s been pretty great - but agree all predecessors were pretty poor

at HP we had a proprietary system for this called “Halo” where they constructed special conference rooms that were meant to feel liek you were sitting around the conference room w/ the remote participant

<http://www.hp.com/hpinfo/newsroom/press_kits/2008/halo/images/G7743001102007.jpg>

<@U053HHEDG>: did you file an issue for jarjar not working with java8?

No, looks like I forgot. I’m working on that now though anyway

Those github code reviews are lie walking into a hen house

Its all cluck cluck cluck nonstop until you leave the house

I'm fine having informal discussions here, but anything that requires wide awareness or consensus should probably (also) be on email.

This looks like its blocking CI on branches: <https://github.com/pantsbuild/pants/issues/2248>
I'll switch to working on it now, but if you hit a shard 1 issue, you'll need to nuke caches to workaround

<@U098ZNTCN>: for example that's killing your branch

Hi 4sq folks, <@U098ZNTCN> told me you guys uses ramdisk for ci, how did you set it up? I tried --pants-workdir=/dev/shm/foo and symlinking .pants.d, neither works due to some pants code expecting things to be inside buildroot

thanks, <@U04S45AHA> was just wondering why <https://travis-ci.org/pantsbuild/pants/jobs/81825553>

<@U0AH2MXCK>: Our entire jenkins executor's workspace lives in the ramdisk

In fact, there are 3-4 executors per worker, and each worker has a 50GB ramdisk

The executors each have a folder in that ramdisk where there's a checkout of the repo where pants runs as normal

I see, so the entire $buildroot is on ramdisk, not just the temporary .pants.d