[WIP] migrates to CircleCI 2.0 #12
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jpbochi
force-pushed
the
circle2
branch
20 times, most recently
from
75b3318 to
b192427
Compare
jpbochi
force-pushed
the
circle2
branch
25 times, most recently
from
131b365 to
bcdfa33
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
docs at https://circleci.com/docs/2.0/migrating-from-1-2/
This seems to not be possible at the moment because CircleCI 2.0 does not support mounting volumes. See https://circleci.com/docs/2.0/building-docker-images/#mounting-folders. Apparently, the workaround is a different "executor type" (see https://circleci.com/docs/2.0/executor-types/), but that is slower and requires more setup, almost defeating the purpose of the update. Also, the "machine" executor might be removed before CircleCI 2.0 gets out of beta.