mirror of
https://salsa.debian.org/raspi-team/image-specs
synced 2026-05-30 06:38:09 +02:00
ad77890ede
Debian's Salsa team has their own registry of images they maintain, so use them instead of ones maintained by gitlab. At https://salsa.debian.org/salsa-ci-team/pipeline/container_registry one can view the various images they maintain. Switch to using 'unstable' instead of 'sid'. The idea is to later also add steps based on 'stable' and then 'unstable' matches better.
30 lines
779 B
YAML
30 lines
779 B
YAML
stages:
|
|
- build
|
|
|
|
variables:
|
|
DEBIAN_FRONTEND: "noninteractive"
|
|
# At https://salsa.debian.org/salsa-ci-team/pipeline/container_registry one can see which images are available
|
|
SALSA_CI_IMAGES: registry.salsa.debian.org/salsa-ci-team/pipeline
|
|
BASE_CI_IMAGES: ${SALSA_CI_IMAGES}/base
|
|
|
|
build:
|
|
stage: build
|
|
image: $BASE_CI_IMAGES:unstable
|
|
retry:
|
|
max: 2
|
|
when: always
|
|
only:
|
|
- branches
|
|
- master # I suppose that we can work directly on master
|
|
- merge_request
|
|
dependencies: []
|
|
script:
|
|
- apt-get update && apt-get install -y vmdb2 dosfstools qemu-utils qemu-user-static debootstrap binfmt-support time kpartx bmap-tools python3 fakemachine make
|
|
- make yaml
|
|
- mkdir build
|
|
- cp raspi*.yaml build
|
|
artifacts:
|
|
paths:
|
|
- build
|
|
|