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.

According to the Posix standard a line of a text is defined as follows:

3.206 Line
A sequence of zero or more non- <newline> characters plus a terminating
<newline> character.

The test checks if this is valid for all newly added or changed text files.

I stumbeled over the issue when adding a new header file the list of header
files used to generate a ROOT dictionary.
The previous last file of the list did not have a proper file ending and
attaching the new header file results in a ROOT dictionary source code with
the following line

'#endif#ifdef'

which could be properly parsed and compiled by the compiler but results in an
error at run time when loading the library.

To avoid such problems in future the test was added.

Only files with unix style file endings should eneter the repository.
Add a CI stage which fails if the file type of a changed file is dos.
Add a script which executes the actaul test.

Pierre-Alain Loizeau authored 4 years ago and Florian Uhlig committed 4 years ago

- Add mcbm_event_reco.C test
- Add mcbm_build_and_reco.C test
- Split CmMake files for mCBM 2019 and 2020 to simplify later cleanup
- Fix tests cleanup for mCBM 2019 and 2020

The CMake version 3.13.4 has a problem to cut the length of test results
to be uploaded to CDash. Using CMake 3.19.1 fixes the problem.

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

Fetch last 100 git commits. Default is 50

Remove obsolete and already commented code.
Remove created artefacts after 1 day automatically.
Install graphiz package needed for doxygen production.

As first stage in the pipline test if the MR branch is up-to-date with the
upstream/master branch. Any further stage is only executed if the MR branch
is up-to-data. This stage was added to avoid running unnecessary pipelines
and not to waste computing ressources.

Don't use cached information when running the CI for changes
in the master branch.

For each commit to the branch nightly_master a build of the doxygen
documentation is triggered. The branch is updated once per night if there
are changes to the master branch. The branch reflects the state of the
master branch at midnight.
The documentation is build using a docker container and the result is
uploaded to the gitlab pages web page at
http://computing.gitpages.cbm.gsi.de/cbmroot/

Implement CI also for macOS. Test merge requests on our macOS 10.13 test system.
The pipline now consists of two steps with three different jobs. First the compliance
with the code formating rules is checked. If this step succeed the code is build and
tested on Linux and macOS. This step runs simultaneous on both platforms.

Only run the piplines when there is a MR to the master branch.
Properly connect the official CbmRoot repository for the format checker
such that the differing source files can be found.
Add a shell script to do this.

Apply code formatting to all source/header files and root macros.

Add line which was removed by accident.

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

Add format check in GitLab CI configuration file.
Add CMake target for format checker .
Add neede CMake files and shell scripts.
Add label in GitLab CI configuration file such that it can be
properly sorted on CDash.
The checker is disabled till we format the complete code base.

Pipeline now fails also in case of failing tests.
New CI option MergeRequest for Dart.sh wrapper which creates a special CDash label.
Use new CI option when GitLab CI runs for a merge request.

This version is an exact copy of the last revision of the trunk branch
of the old SVN repository of CbmRoor at
https://subversion.gsi.de/cbmsoft/cbmroot/trunk
The old SVN repository will still be available for read access.