Hibbian
/
Raspi-image-spec
1
0
Fork 0
Code Issues 3 Pull Requests Packages Projects Releases Wiki Activity
Raspi-image-spec/debian/salsa-ci.yml

35 lines
966 B
YAML
Raw Normal View History

ci: Add 'check yamls' job in (new) 'check input' stage Add a new stage 'check input' to our CI configuration to check whether our input files contain errors. The first check is for the YAML files whether they contain errors or warnings according to 'yamllint'. Add 'yamllint' config file to not consider too long lines as errors. And fix the errors/warnings in 'salsa-ci.yml' itself. Apparently job names can contain space, so rename 'build-yamls' to 'build yamls'.
2022-11-11 18:05:57 +00:00
---
Add basic .gitlab-ci.yml
2022-11-03 20:43:17 +00:00
stages:
ci: Add 'check yamls' job in (new) 'check input' stage Add a new stage 'check input' to our CI configuration to check whether our input files contain errors. The first check is for the YAML files whether they contain errors or warnings according to 'yamllint'. Add 'yamllint' config file to not consider too long lines as errors. And fix the errors/warnings in 'salsa-ci.yml' itself. Apparently job names can contain space, so rename 'build-yamls' to 'build yamls'.
2022-11-11 18:05:57 +00:00
# Garbage in is garbage out, so verify our input
- check input
Add basic .gitlab-ci.yml
2022-11-03 20:43:17 +00:00
- build
Move some lines to other position in the file It's common to define variables/constants in the top of a file, so do that here too. Move 'stage' field directly under step name as it's quite significant and seen in other salsa-ci.yml as well. Move 'image' line after 'stage' line as it's quite important as well.
2022-11-03 20:54:38 +00:00
variables:
DEBIAN_FRONTEND: "noninteractive"
Switch to using images maintained by salsa ci team 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.
2022-11-03 20:55:32 +00:00
# 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
Move some lines to other position in the file It's common to define variables/constants in the top of a file, so do that here too. Move 'stage' field directly under step name as it's quite significant and seen in other salsa-ci.yml as well. Move 'image' line after 'stage' line as it's quite important as well.
2022-11-03 20:54:38 +00:00
ci: Add 'check yamls' job in (new) 'check input' stage Add a new stage 'check input' to our CI configuration to check whether our input files contain errors. The first check is for the YAML files whether they contain errors or warnings according to 'yamllint'. Add 'yamllint' config file to not consider too long lines as errors. And fix the errors/warnings in 'salsa-ci.yml' itself. Apparently job names can contain space, so rename 'build-yamls' to 'build yamls'.
2022-11-11 18:05:57 +00:00
check yamls:
stage: check input
image: $BASE_CI_IMAGES:unstable
dependencies: []
script:
- apt-get update && apt-get upgrade -y
- apt-get install -y yamllint
- yamllint -c debian/yamllint.yml .
build yamls:
Move some lines to other position in the file It's common to define variables/constants in the top of a file, so do that here too. Move 'stage' field directly under step name as it's quite significant and seen in other salsa-ci.yml as well. Move 'image' line after 'stage' line as it's quite important as well.
2022-11-03 20:54:38 +00:00
stage: build
Switch to using images maintained by salsa ci team 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.
2022-11-03 20:55:32 +00:00
image: $BASE_CI_IMAGES:unstable
Add basic .gitlab-ci.yml
2022-11-03 20:43:17 +00:00
dependencies: []
script:
Upgrade pkgs separately before installing new ones Upgrade the existing packages before installing new ones. It's better to have a fully up-to-date system to work on and it could also fix/prevent an installation issue if a package depends on an existing, but un-upgraded one. With this change we get "and 0 not upgraded", which was not always the case before. Also add a '/' after the 'build' directory to make it clear it is a dir.
2022-11-05 11:23:03 +00:00
- apt-get update && apt-get upgrade -y
- eatmydata apt-get install -y vmdb2 dosfstools qemu-utils qemu-user-static debootstrap binfmt-support time kpartx bmap-tools python3 fakemachine make
Add basic .gitlab-ci.yml
2022-11-03 20:43:17 +00:00
- make yaml
- mkdir build
Upgrade pkgs separately before installing new ones Upgrade the existing packages before installing new ones. It's better to have a fully up-to-date system to work on and it could also fix/prevent an installation issue if a package depends on an existing, but un-upgraded one. With this change we get "and 0 not upgraded", which was not always the case before. Also add a '/' after the 'build' directory to make it clear it is a dir.
2022-11-05 11:23:03 +00:00
- cp raspi*.yaml build/
Add basic .gitlab-ci.yml
2022-11-03 20:43:17 +00:00
artifacts:
paths:
Upgrade pkgs separately before installing new ones Upgrade the existing packages before installing new ones. It's better to have a fully up-to-date system to work on and it could also fix/prevent an installation issue if a package depends on an existing, but un-upgraded one. With this change we get "and 0 not upgraded", which was not always the case before. Also add a '/' after the 'build' directory to make it clear it is a dir.
2022-11-05 11:23:03 +00:00
- build/