Commit af61d151 authored by GILLES Sebastien's avatar GILLES Sebastien

#177 CI: add another possibility to trigger a full analysis in yaml files.

parent 70bf4908
......@@ -13,6 +13,7 @@ cppcheck:
only:
- develop@morefem/corelibrary/morefem
- /(sonarqube)/
- /(full_ci_analysis)/
rats:
......@@ -30,6 +31,7 @@ rats:
only:
- develop@morefem/corelibrary/morefem
- /(sonarqube)/
- /(full_ci_analysis)/
clang-static-analysis:
......@@ -46,6 +48,7 @@ clang-static-analysis:
only:
- develop@morefem/corelibrary/morefem
- /(sonarqube)/
- /(full_ci_analysis)/
sonarqube:
......@@ -69,6 +72,7 @@ sonarqube:
only:
- develop@morefem/corelibrary/morefem
- /(sonarqube)/
- /(full_ci_analysis)/
......@@ -19,6 +19,7 @@
only:
- develop@morefem/corelibrary/morefem
- /(valgrind)/
- /(full_ci_analysis)/
allow_failure: true
......
......@@ -9,7 +9,6 @@ A HPC finite element library developed for the implementation of the models of M
- [Installing compilers on Ubuntu](#installing-compilers-on-ubuntu)
- [Installing compilers on Fedora](#installing-compilers-on-fedora)
+ [Third-party libraries](#third-party-libraries)
+ [FYI: Embedded libraries](#fyi-embedded-libraries)
* [MoReFEM compilation](#morefem-compilation)
+ [XCode](#xcode)
+ [CMake](#cmake)
......@@ -19,8 +18,9 @@ A HPC finite element library developed for the implementation of the models of M
* [Structure of the source code](#structure-of-the-source-code)
- [How to contribute](#how-to-contribute)
- [Continuous integration](#continuous-integration)
- [Static analysis / Sonarqube](#static-analysis--sonarqube)
- [Documentation](#documentation)
* [Basic use: on each push](#basic-use-on-each-push)
* [More thorough jobs](#more-thorough-jobs)
* [Setting up CI for your fork](#setting-up-ci-for-your-fork)
* [Doxygen](#doxygen)
* [Introduction talks](#introduction-talks)
* [Lexicon](#lexicon)
......@@ -268,10 +268,11 @@ There are additional optional steps also available in CI:
- One named 'valgrind', which runs Valgrind on the embedded models and on few tests.
- One named 'analysis', which runs several static analysis tools. Another stage 'sonarqube' aggregates the results and put them on a [Sonarqube](https://sonarqube.inria.fr/sonarqube)] instance.
There are two ways to kick in these stages:
There are three ways to kick in these stages:
- Push onto 'develop' branch of the main project (reserved for the integrator - i.e. myself only for the time being).
- Push onto a branch which include 'valgrind' (for Valgrind) and 'sonarqube' (for the static analysis) in its name. Both may be combined: if you push to a branch named 10000_new_feature_sonarqube_valgrind all will be triggered.
- Push onto a branch which include 'valgrind' (for Valgrind) or 'sonarqube' (for the static analysis) in its name. Both may be combined: if you push to a branch named 10000_new_feature_sonarqube_valgrind all will be triggered.
- Push onto a branch which name include 'full_ci_analysis'. This will trigger everything. Currently it's equivalent to putting 'sonarqube' and 'valgrind' in the name of the branch, but if additional optional stages are added they will be automatically be encompassed there.
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).
......
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