...
- 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
Code Block title .gitlab-ci.yml linenumbers true stages: - Test Docker Execution inside Docker container: stage: Test Docker tags: - Docker image: 'gitlab.eufus.psnc.pl:5050/g2michal/imas-based-docker/ual-fc2k' before_script: - module load IMAS - imasdb test - git clone https://$CREDENTIALS@github.com/mkopsnc/beaver-data.git - tar -xf beaver-data/data/input/input.tar.gz -C $HOME/public/imasdb/test/3/0 script: - make - ./bin/main
Warning The ual-fc2k is a private repository. You have to request access in order to use Docker image
- Complete each section. Remember that each project has different requirements, so the commands must be adapted to your code.
- image - allows to specify a custom Docker image and a list of services that can be used for time of the build
tags - The tag indicates whether the task is to be performed by HPC or Docker.
Use Docker in this example. Using HPC is described hereInfo Our 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