mirror of
https://salsa.debian.org/raspi-team/image-specs
synced 2026-05-30 06:38:09 +02:00
02567af307
As we're just starting out using CI, it is especially important to be aware of any failure, so that we can fix it. Such a workaround can be added later in case it is deemed necessary.
27 lines
748 B
YAML
27 lines
748 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-yamls:
|
|
stage: build
|
|
image: $BASE_CI_IMAGES:unstable
|
|
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
|
|
|