Commit 9c458810 authored by GILLES Sebastien's avatar GILLES Sebastien

#0 Update the README to detail the new CI environment variable required.

parent 11202c2e
......@@ -275,7 +275,9 @@ There are three ways to kick in these stages:
- Push onto a branch which include 'valgrind' (for Valgrind), 'sonarqube' (for the static analysis) or 'verrou' (for floating-point precision) in its name. Several may be combined: if you push to a branch named 10000_new_feature_sonarqube_valgrind both sonarqube and valgrind will be triggered (but not verrou),.
- Push onto a branch which name include 'full_ci_analysis'. This will trigger everything.
For the Sonarqube stage, you need to define the environment variable `SONARQUBE_LOGIN` in the gitlab fork of MoReFEM, and assign to it the token generated on your [Sonarqube account](https://sonarqube.inria.fr/sonarqube/account/security).
For the Sonarqube stage, you need to define two environment variables in the gitlab fork of MoReFEM:
- `SONARQUBE_LOGIN` , and assign to it the token generated on your [Sonarqube account](https://sonarqube.inria.fr/sonarqube/account/security).
- `SONARQUBE_PROJECT` and assign to it what will be an identifier for your project. Typically put your identifier (i.e. `sgilles`; this variable was actually introduced for the main repository).
## Setting up CI for your fork
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment