These variables are necessarily set due to initial declarations
at the top of gitlab-ci.yml.

As quality should be checked, a failing stage is introduced to keep
integrator aware.

Cf. https://docs.gitlab.com/ee/user/project/merge_requests/test_coverage_visualization.html

Sébastien Dinot authored 4 years ago and Luc Maisonobe committed 4 years ago

'sonar.projectKey' and 'sonar.projectName' properties were not set on
the Maven command line. Because of their default values, they had the
same value for all Orekit forks. All analysis reports were therefore
pushed in the same SonarQube project, which was not appropriate. This
modification will improve the CI behavior by setting a specific value
for these proprerties for each fork.

An archive for sources can be downloaded
directly from Gitlab, in pages related to
tags or releases.

This image embed both maven and graphviz.

The site goal triggers tests if run alone.

The site phase requires verification results.

Tests have been done some job before.