From 4684b443bbe71bd9b7acd7a4b5aec5160031ae71 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lo=C3=AFc=20Hoguin?= Date: Mon, 4 Jun 2018 12:04:40 +0200 Subject: Update user guide --- guide/ci.html | 13 +++++-------- 1 file changed, 5 insertions(+), 8 deletions(-) (limited to 'guide/ci.html') diff --git a/guide/ci.html b/guide/ci.html index 5705b07..998c3cf 100644 --- a/guide/ci.html +++ b/guide/ci.html @@ -33,24 +33,21 @@ div.navfooter{margin-bottom:1em}
-
Prev   Next

Chapter 21. Continuous integration

Erlang.mk comes with some support for continuous integration, +

Prev   Next

Chapter 22. Continuous integration

Erlang.mk comes with some support for continuous integration, aimed at open source projects that need to support more than one specific Erlang/OTP release. (If you target one specific release, check the OTP version pinning -Section 12.2, “OTP version pinning” -section of the OTP version management -Chapter 12, OTP version management chapter.)

21.1. Configuring Erlang/OTP versions to test

To use the CI plugin you must first configure which versions +section of the OTP version management chapter.)

22.1. Configuring Erlang/OTP versions to test

To use the CI plugin you must first configure which versions of Erlang/OTP will be used. Erlang.mk provides three separate configuration variables depending on whether you need a normal OTP release, a HiPE-enabled release or an ErLLVM-enabled release.

At the time of writing, this is how you would test against all the most recent patch releases of Erlang/OTP 19 and above:

CI_OTP = OTP-19.0.7 OTP-19.1.6 OTP-19.2.3 OTP-19.3.6.2 OTP-20.0.4

If you want to test against HiPE and ErLLVM but only with the latest version of Erlang/OTP, the following could work:

CI_HIPE = $(lastword $(CI_OTP))
-CI_ERLLVM = $(CI_HIPE)

Consult the OTP version management -Chapter 12, OTP version management chapter for more +CI_ERLLVM = $(CI_HIPE)

Consult the OTP version management chapter for more information about Erlang/OTP versions and customization of the -Erlang/OTP builds.

21.2. Running tests across all configured versions

The recommended way to run the ci target is with the option +Erlang/OTP builds.

22.2. Running tests across all configured versions

The recommended way to run the ci target is with the option -k. It will ensure that tests are run for all configured -Erlang/OTP versions, even if there are errors:

$ make ci -k

21.3. Extending the CI targets

The ci target can be extended. For example to run Dialyzer +Erlang/OTP versions, even if there are errors:

$ make ci -k

22.3. Extending the CI targets

The ci target can be extended. For example to run Dialyzer at the end of CI:

ci:: dialyze

Additional setup can be done by extending the ci-setup target. This target is ran before testing each individual Erlang/OTP version.

For example, to ensure dependencies are re-fetched/built -- cgit v1.2.3