Diane Trout:
> Can you trigger test on dependencies changing?
You can cron test runs, that would then check the deps.
> Does CI run on architectures other than amd64?
That depends on the gitlab-ci-runners that are registered. Anyone can
register CI-runners for their own projects, and CI runner
Can you trigger test on dependencies changing?
Does CI run on architectures other than amd64?
(I was thinking of complex packages with many dependencies like dask,
or with fiddly bit manipulation like pandas)
So this would get tests on each commit instead of the current
autopkgtests which run on
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
H
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
buil
4 matches
Mail list logo
