Skip to content
Snippets Groups Projects

Drop obsolete infrastructure documents focusing on Jenkins

Merged Drop obsolete infrastructure documents focusing on Jenkins
wip/em/drop-obsolete-jenkins-documents into master
All threads resolved!
Merged Emanuele Aina requested to merge wip/em/drop-obsolete-jenkins-documents into master
All threads resolved!
Viewing commit 845c6435
Show latest version
2 files
+ 12
− 6
Compare changes
  • Side-by-side
  • Inline
Files
2
  • 845c6435 
    This document describes how we built images on Jenkins, but we have now
largely moved away from it in favor of GitLab CI/CD.

The README in the infrastructure/apertis-image-recipes> project
describes the current setup closer to the actual code.

Keep the document around since v2019 and v2020 are still officially on
Jenkins and old release notes still point here.

Signed-off-by: Emanuele Aina's avatarEmanuele Aina <emanuele.aina@collabora.com>
content/architecture/long-term-reproducibility.md
+ 4
− 4
@@ -100,9 +100,9 @@ they get triggered.
In some cases, losing access to the build environment effectively means that
a project can't be maintained anymore, as no new build can be made.
To be able to avoid these issues as much as possible, Apertis makes heavy use
of [isolated containers based on Docker
images](image-build-infrastructure.md#docker-images-for-the-build-environment).
To be able to avoid these issues as much as possible, Apertis makes heavy
use of
[isolated containers based on Docker images](https://gitlab.apertis.org/infrastructure/apertis-image-recipes/#building-in-docker)
All the Apertis build pipelines run in containers with minimal access to
external resources to keep the impact of the environment as low as possible.
@@ -145,7 +145,7 @@ and the main build process.
## Build recipes
The process to the reference images is described by textual, YAML-based
[Debos recipes]( {{< ref "image-build-infrastructure.md#image-building-process" >}} ) stored in
[Debos recipes](https://gitlab.apertis.org/infrastructure/apertis-image-recipes/)
git repository, with a different branch for each release channel.
The textual, YAML-based GitLab-CI pipeline definitions then control how the
Apertis Website Terms of Use Privacy Policy