Since I got only crickets on this email, let me elaborate: gitlab-ci lets you run whatever you want as root via Docker images. That means its easy to run full builds, installs, and tests in gitlab-ci. It also makes it easy to add CI tests for various releases, like to support backports.
.hc Hans-Christoph Steiner: > > One great addition that GitLab gives us is CI builds with custom Docker > images, which will run the whole build/test process for each merge > request. For example: > > https://salsa.debian.org/eighthave/python-vagrant/-/jobs/4005 > > I have set up a prototype Docker image for running git-buildpackage > builds automatically. This Docker image is built and deployed using > Gitlab CI (albeit on gitlab.com): > > https://gitlab.com/eighthave/ci-image-git-buildpackage > > Then any git-buildpackage package can be built by doing this: > > * put git project on salsa > * In Settings -> CI/CD -> General pipelines settings -> > Custom CI config path, set it to: debian/.gitlab-ci.yml > * include debian/.gitlab-ci.yml in the git repo with this contents: > > > > image: registry.gitlab.com/eighthave/ci-image-git-buildpackage:latest > > build: > artifacts: > paths: > - *.deb > expire_in: 1 day > script: > - /gitlab-ci-git-buildpackage > - dpkg -i ../*.deb || apt-get install -f > - mv ../*.deb . > > > > I think we can do a lot of automation in the Docker image, like some of > the stuff I've already done in ci-image-git-buildpackage. If someone > knows how to get ENTRYPOINT and/or CMD working with GitLab CI, then > /gitlab-ci-git-buildpackage could be run automatically. > > .hc >
