- move Gaudi::Funtional to GaudiFunctional subdir
  - headers are now under "Gaudi/Functional"
  - legacy GaudiAlg corresponding header redirect to the new ones
- replace GaudiAlgorithm with Algorithm wherever possible in tests and
  utilities
- add Gaudi::Sequencer basic implementation to replace GaudiSequencer
- move GaudiAlg specific tests, examples, dictionaries and Python modules
  to GaudiAlg subdir
- add CMake option GAUDI_ENABLE_GAUDIALG to allow skipping GaudiAlg
  (default to true)
- minor fixes and clean ups

- change default LCG to 103
- run build and test in one job
- test centos7 and el9
- use LCG 102b x86_64-centos7-gcc11-opt as minimum version

With `ctest --repeat until-pass:3`, tests are run until successful or
at most 3 times. Tests are retried on any failure (timeout or other).

do not use LHCb CVMFS for LCG views

This is closer to the original QMTest behaviour and makes it possible
to add HTML code in the reports.

Try to build GaudiKernel a few times reducing the concurrency at each
iteration to make sure we succeed. Then rebuild from scratch to get
a clean build log.

- use gitlab pipeline DAG
- add build-check for lhcb-gcc9
- add py3 build
- restore formatting and copyright checks

Thomas Cluzel authored 4 years ago and Marco Clemencic committed 4 years ago

see https://its.cern.ch/jira/browse/LBCOMP-23



Co-authored-by: Marco Clemencic <marco.clemencic@cern.ch>

Add a new set of jobs `build-check:...` that would pass if there are no
warnings and would "fail" otherwise. Since the job is allowed to fail,
the failure would be reflected as a yellow job/pipeline status.

which means use LCG_XYpython3 instead of LCG_XY