-
-
Notifications
You must be signed in to change notification settings - Fork 652
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Re-structure CI flow. #6214
Re-structure CI flow. #6214
Conversation
First build pants pexes for OSX and Linux and then use those pexes to run all tests in a subsequent stage. Fixes pantsbuild#6016
…ux shard, yet internally only activated for darwin - so it looks like this never could have worked, except when run in Docker on OSX, which means a local OSX user who could do these things by hand.
…ecuting python interpreter.
034b92a
to
bf42e37
Compare
Note to self: TODO downgrade bash / do not use |
…and ensure travis cache hits across linux shards.
…'t exist downstream.
… container due to absolute path mismatches.
…ify stage: names since we now use descritive name:
Getting bit by pantsbuild/binaries#78 |
Note to self: the pants venv is no longer in play which means any extra 3rdparty deps used by plugins but not core pants will not be seen by pants.pex. One solution is overriding backends with plugins in the CI-specific pants.ini. Another is to back out PANTS_COMMAND changes and instead cache ~/.cache/pants/bin/native-engine/. |
First build pants pexes for OSX and Linux and then use those pexes to
run all tests in a subsequent stage.
Fixes #6016