Skip to content
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

Upgrade to CircleCI 2.0 #1

Merged
merged 11 commits into from Aug 4, 2017
Merged

Upgrade to CircleCI 2.0 #1

merged 11 commits into from Aug 4, 2017

Conversation

randycoulman
Copy link
Owner

Upgrade CI support to CircleCI 2.0.

This requires a new configuration file: .circleci/config.yml replaces circle.yml.

Since CircleCI is based on Docker images, we no longer need to manually install Elixir and Erlang via asdf, so I was able to delete scripts/install_elixir.sh.

I did run into one issue, however. The default resource_class on CircleCI 2.0 doesn't appear to have enough memory to run mix dialyzer --plt the first time, so it gets killed, failing the build.

I have a support request in to CircleCI, but for now I have disabled the Dialyzer steps of the CI build.

Trying more RAM to see if I can keep dialyxir from getting killed.
Resource class configuration is not enabled by default, so turning off
the memory-intensive dialyzer steps for now to get to green.

I may choose to request access to another resource class once this is
green.
- Add (commented-out) cache for Dialyzer PLT
- Add version number prefixes to cache keys
- Fallback to generic cache if specific cache not available
It's not supported yet for this project.
Checking if resource_class is enabled for my account yet.
resource_class is still not enabled
@randycoulman
Copy link
Owner Author

Still can't get dialyzer to run successfully the first time, but merging anyway. There's been some memory usage improvements in dialyzer in Elixir/OTP 20, so perhaps an upgrade will help.

@randycoulman randycoulman merged commit 730988b into master Aug 4, 2017
@randycoulman randycoulman deleted the circleci-2.0 branch August 4, 2017 13:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant