1. How to use Gateway runner?
1.1. Set up of simple CI/CD
- Log in to gitlab.eufus.psnc.pl
- On the top bar, select Menu > Projects and find your project
- Press "+" button and select New File
- File must be in root of your repository and be called gitlab-ci.yml
Prepare content for CI / CD purposes - you can use simple example below as a template
.gitlab-ci.ymlstages: - Test IMAS Test IMAS environment: stage: Test IMAS tags: - HPC before_script: - eval `/usr/bin/modulecmd bash load cineca` - eval `/usr/bin/modulecmd bash load imasenv` - mkdir test-database - imasdb `pwd`/test-database # a hack to allow installing imasdb in custom folder (non ~/public) - export ids_path="`pwd`/test-database;$ids_path" script: - python3 ids_put.py - python3 ids_get.py after_script: - rm -rf `pwd`/test-database - eval `/usr/bin/modulecmd bash purge`
There is a hack to allow installing imasdb in custom folder (non ~/public):
- imasdb `pwd`/test-database- Complete each section. Remember that each project has different requirements, so the commands must be adapted to your code.
tags - The tag indicates whether the task is to be performed by HPC or Docker.
Use HPC in this example. Using Docker is described hereOur GitLab's CI/CD is using HPC on Gateway. This means that the script commands will be called and run like on Gateway
- before_script - is used to define the command that should be run before all builds, including deploy builds
- script - defines a shell script which is executed by Runner
- after_script - is used to define the command that will be run after for builds
- At the end press Commit changes
1.2. How to check my CI/CD tasks?
Please visit this page