Closed kdave closed 1 year ago
Other than that, looks like its some kind of gitlab network issue, I don't think cli-tests
takes 1hr! https://gitlab.com/kdave/btrfs-progs/-/jobs/333296786
@kdave, Since you already have kernel and debian image from these existing jobs:
https://gitlab.com/kdave/btrfs-progs/-/jobs/338844201 https://gitlab.com/kdave/btrfs-progs/-/jobs/338844202
If required, you can reuse those images by making below .gitlab-ci.yml changes:
BUILD_KERNEL: "0"
PREBUILT_KERNEL_ID: "338844201"
BUILD_IMAGE: "0"
PREBUILT_IMAGE_ID: "338844202"
This seems to be fragile, first generate, then update CI script with the ids. What if I want to rebuild the base image or kernel every now and then? The images are cached at the CI, the cache can be invalidated (ie. the files removed), so this would be the way to regenerate them. I'd expect the script can see if the image exists and use it, otherwise rebuild.
So we will check whether required kernel or base image exists in CI cache or not. If its not available, then build it. That looks much better approach than current one. Let me read about CI cache stuff.
I'm going to disable the Gitlab CI since v5.10 as it has been failing due to the slow qemu.
Also travis-ci.org will be shut down and travis-ci.com does not provide the exactly same service so we may need to search again for a CI.
I have a working Dockerfile running the testsuite, so this should become the replacement of the remote CI. With some github integration it could do the same post-commit checks on devel, though without the nice gui to review results. With the docker example it should be possible to add more distros (now it's on openSUSE Tumbleweed) and run on custom kernels, or convert to another container infrastructure.
Docker images for openSUSE and CentOS are now in devel.
Travis CI will be disabled since v5.12.
Github actions CI work in progress.
Now enabled for devel, more work still needed but basic build and test is covered, closing.
Travis CI does not provide an updated system image and tests fail for that reason. We can't use that for development testing. Look for a better CI hosting.
Requirements: