Explain how to customize INRIA's CI for custom branches
parent
4a6e431e8f
commit
1d20e28d98
15
HACKING.adoc
15
HACKING.adoc
|
@ -307,6 +307,21 @@ OCaml's GitHub repository and then push "mybranch" to your fork.
|
|||
7. You should receive a bunch of e-mails with the build logs for each
|
||||
slave and each tested configuration (with and without flambda) attached.
|
||||
|
||||
==== Changing what the CI does
|
||||
|
||||
INRIA's CI "main" and "precheck" jobs run the script
|
||||
tools/ci-build. In particular, when running the CI on a publicly
|
||||
available branch via the "precheck" job as explained in the previous
|
||||
section, you can edit this script to change what the CI will test.
|
||||
|
||||
For instance, parallel builds are only tested for the "trunk"
|
||||
branch. In order to use "precheck" to test parallel build on a custom
|
||||
branch, add this at the beginning of tools/ci-build:
|
||||
|
||||
----
|
||||
OCAML_JOBS=10
|
||||
----
|
||||
|
||||
=== The `caml-commits` mailing list
|
||||
|
||||
If you would like to receive email notifications of all commits made to the main
|
||||
|
|
Loading…
Reference in New Issue