You will need roughly 2 minutes to read this article.
The easiest way to do this is by using our scripts repository, specifically the Erlang and Elixir scripts both. After connecting your repository, you can add these setup commands that will automatically download Elixir and Erlang. Both are needed to be able to run Elixir.
source /dev/stdin <<< "$(curl -sSL https://raw.githubusercontent.com/codeship/scripts/master/languages/erlang.sh)" source /dev/stdin <<< "$(curl -sSL https://raw.githubusercontent.com/codeship/scripts/master/languages/elixir.sh)"
The setup looks like this:
Installing dependencies via hex is supported once Elixir has been installed, as per the instructions above.
We do not cache Elixir dependencies between builds.
Elixir frameworks such as Phoenix, and test tools such as ExUnit, are all supported on Codeship. Note that you will need to manually install all tools needed, in your project’s setup commands.
If you are running parallel test pipelines, you will want separate your tests into groups and call a group specifically in each pipeline. For instance:
mix test tests/tests_1.exs
mix test tests/tests_2.exs
In addition to parallelizing your tests explicitly via parallel pipelines, some customers have found using ExUnit’s built-in test parallelization is a good way to speed up your tests.
Note that aggressive parallelization can cause resource and build failure issues, as well.
Due to Elixir version and build issues, you may find it helpful to tests your commands with different versions via an SSH debug session if tests are running differently on Codeship compared to your local machine.
Do you think we need to improve this article? If so, please submit our feedback form to help us improve this article!