Next Steps and Things to Try

The examples we have just implemented into our projects are very basic, the possibilities with CI/CD are endless.

Run our tests

It is quite common for ATLAS repositories to run tests in their GitLab CI.

One simple thing to try would be to get the GitLab CI to run the CMake tests you hopefully were able to use earlier in the CMake tutorial. Maybe even create your own test

Run over our data file

Now that you can compile your code, the next step would be to access the file from cvmfs/eos on GitLab and run your code.

Unfortunately we were unable to make the GitLab runners execute over our test file. However, this is possible! It requires a little bit of setup but if there is time, look into accessing data using GitLab CI. It would either require a CERN service account or letting GitLab CI know your username and password for eos. If you wish to take on this step, let one of the instructors know. Note this may require setting authentication variables

Some resources that might help:

• Using Giordon’s slides
• example .gitlab-ci.yml,
• HSF Training

More advanced (and maybe beyond the scope)

• Perhaps your repo is updating software used by others and you want to ensure that it is always working and robust. As such, instead of just running your tests when a change is made, go discover how you can schedule automatic runs of your pipeline tests to occur on a recurring basis, like once per day. (If you are not sure of where to start, try googling, and then asking on the Discord)

---