Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

AlmaLinux 9 image for CI #83

Merged
merged 2 commits into from
Apr 4, 2024
Merged

AlmaLinux 9 image for CI #83

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7def518
link to alma9-base image in CI
mmikhasenko Apr 4, 2024
471f59e
link to container registry
mmikhasenko Apr 4, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions git/11-ci.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ with each job having it's own environment. A minimal example of this file is:

```yaml
my_first_job:
image: gitlab-registry.cern.ch/ci-tools/ci-worker:cc7
image: gitlab-registry.cern.ch/linuxsupport/alma9-base
script:
- python -c 'import this'
- echo "My first CI produced file" > output.txt
Expand All @@ -39,7 +39,8 @@ my_first_job:
This creates a single job named `my_first_job` and the `image:` key defines a
[docker image](https://www.freecodecamp.org/news/a-beginner-friendly-introduction-to-containers-vms-and-docker-79a9e3e119b/)
which is used the define the environment that is used to run the job. In this case we use an
[official CERN CentOS 7 image](https://gitlab.cern.ch/ci-tools/ci-worker/container_registry).
[official CERN AlmaLinux 9 image](https://gitlab.cern.ch:/linuxsupport/alma9-base/container_registry).
More images are listed at the [documentation pages](https://linux.web.cern.ch/dockerimages/) for linux at CERN.
The `script:` key then defines one or more commands which are executed
sequentially. If any of the command return a non-zero exit code the execution
stops and the "build" is marked as failed.
Expand Down