Instead of using the Singularity runtime to execute the test in containers the
successor Apptainer is used.

Use the Apptainer (successor of Singularity) runner to test CbmRoot on a
Debian12 container. Debian12 (bookworm) will be released mid of June.
So the MR adds a test for Debian12 as well as a new container runtime
environment.

Test CbmRoot with FairSoft nov22p1 and FairRoot v18.8.0 on macosx13.

After FairSoft nov22p1 and FairRoot v18.8.0 are released test CbmRoot with
these releases on CentOS 7, Debian 10, macosx 11 and macosx 12.

Add CI test with FairSoft nov22rc and FairRoot v18.8_patches.

Administrator authored 2 years ago and Florian Uhlig committed 2 years ago

Use a different installation directory For the test of the installation to
allow to remove also the build directory.

Test installation also on Debian 10

There was a problem when running CbmRoot from the installation directory with
Debian10. So add also the installation test for Debian10.

The external flesnet requires at least CMake 3.14.0.
Check already in our CMakeLists.txt if this version is available, otherwise
the test is done when building flesnet and the error is hidden in some log
file.
Use CMake from the FairSoft installation on the CI runner (lxir116 )where the
CMake version is to old.

Use qemu instead of VirtualBox to execute the virtual machines.
The advantage is a much faster and reliable startup of the VMs.
With VirtualBox the image needs to be copied as well there were sometimes
problems with the ssh connection to a running machine.
With qemu the copy of the image isn't needed and no ssh problems were
seen yet.

Administrator authored 2 years ago and Volker Friese committed 2 years ago

Remove builds which use old and unsupported FairSoft and FairRoot versions.
Update FairSoft and FairRoot versions for real data test.
Add missing dependency for clang-format checks.

Use also for macosx 11 the latest FairSoft and FairRoot release versions# Please enter the commit message for your changes. Lines starting

Remove Debian8 systems from the CI pipeline.
Use FairSoft apr21p2 and FairRoot v18.6.7 for tests.

Administrator authored 3 years ago and Florian Uhlig committed 3 years ago

Machine is now running with Debian10.
Only set the proper CVMFS paths,

Machine was upgraded to a new OS.

Use FairSoft apr21p1 and FairRoot v18.6.4 for the test.

Eoin Clerkin authored 3 years ago and Florian Uhlig committed 3 years ago

Ensures that modified .cpp, .C and .h files follow basic licence header guidelines.

Check line 1 for a copyright declaration with correct numerial and character placements for a date followed by institute and city.
Check line 2 for SPDX licence identifier.
Check line 3 for author and committer information.

The machine providing the CbmRoot_macosx gitlab-runner is currently broken.

After the long standing problem with the external package AnalysisTree was
fixed the tests with the latest FairSoft/FairRoot versions are enabled.
Test on Debian 8, Debian 10 and CentOS 7.

Increase the depth of the shallow clone done by GitLab.
If the number of commits is larger than the depth, the head of the
upstream/master is not in the history otherwise.
This fixes a problem of !399.

Add tests for  macosx 10.15 and 11 on our new runners.
Retire old test on macosx 10.13.

Define number of CPUs in runner configuration.

Move the definition from the global gitlab CI configuration to the local
runner configurations.
Defining the number of CPUs in the runner configuration allows to adjust this
value to the actual underlying hardware.

This pipline only runs when merging a merge request.

Administrator authored 3 years ago and Florian Uhlig committed 3 years ago

There is a known but yet not fixed issue with the latest FairSoft (ROOT)
version and the Analystree package which breaks the test suite.
Since we don't use the version anyway the test is remove from the pipeline
till the issue is fixed.

Administrator authored 3 years ago and Florian Uhlig committed 3 years ago

Add new combinations of FairSoft/FairRoot to the Debian8 tests which
are executed on the singularity runner

Pass additional flags to CTest.

Cleanup the script.

Administrator authored 3 years ago and Florian Uhlig committed 3 years ago

If defined run a configuration script before executing CTest.
This is needed for example to define newer compiler or cmake versions.

Administrator authored 3 years ago and Florian Uhlig committed 3 years ago

Beside the existing debian10 test, now  also debian8 is tested.
Limit the number of used CPUs to 14 such that 4 concurrent jobs
don't interfere with each other.

Administrator authored 3 years ago and Florian Uhlig committed 3 years ago

Store variables and job template separatly and put them together for the job.
With only one job this doesn't make sense yet but if more jobs are added the
definition of the new jobs become much more easy and the duplicated code is
removed.

Administrator authored 3 years ago and Florian Uhlig committed 3 years ago

Move variables out of the script. If this works the script can be used
by any of our runners.

Administrator authored 3 years ago and Florian Uhlig committed 3 years ago

Add a new computer with a singularity runner. Currently the image is
fixed to debian10. If the runner correctly works the scheme can be
expanded to other OS. This is currently a test if the runner is
implemented correctly and properly picks up the work.

For the continuous tests rerun failed tests a second time. This should reduce
the number of failing test pipelines.
In most cases of failing tests the Geant3 simulations crash due to the well
known memory error. If these tests are restarted they normally work without
problem.
Since the feature to restart tests is only available with cmake 3.17 change
the scripts of the CI pipeline to use at least this version.

Fix the stage for the rebase check.
After the upgrade it lloks like that the pipeline doesn't run any longer in
the context of the forked project but in context of the master project such
that the project path wasn't correct any longer. This allows now to compare
upstream/master to HEAD.

Florian Uhlig authored 4 years ago and Volker Friese committed 4 years ago

Implement code owner functionality for our CI. Code owners are identified on a directory base by a look-up file. They are notified when changes to their code included in a MR.