ci: Forgejo pipeline, integration tests on sites from Checkmk's packages #1
Loading…
Reference in a new issue
No description provided.
Delete branch "ci-pipeline"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Moves CI to Forgejo and runs the integration tests there for the first time.
.forgejo/workflows/ci.yml, on pushes to main andrenovate/all-patch, pull requests, and every Monday):tests/integration/packages.pytakes the newest 2.4 (Raw) and 2.5 (Community) patch releases for Debian 12 fromstable_downloads.jsonand checks each download against the SHA-256 listed there.tests/integration/image/Dockerfile). The update test runsomd updatefrom 2.4 to 2.5 in the same container, as on a server.v*tag publishes the MKP and its SHA256SUMS (release.yml). The tag must matchbuild.py's version..cz.tomllets the release bot bumpbuild.pyand the install commands in the README.requirements-test.txtup to date;.github/workflows/test.ymlis removed.First run on real sites: locally, all 30 integration tests passed on 2.4.0p41 and 2.5.0p20, with the update. Two tests were fixed:
mkpinstalls files with the site's umask 0077 (mode 0600), which is correct;Tests of CI / unit: passed
34 passed, 0 failed, 0 skipped (34 tests, 16.2 s)
Of
b06d999aee, the run, updated by every run.Tests of CI / integration: passed
30 passed, 0 failed, 0 skipped (30 tests, 733.5 s)
Of
b06d999aee, the run, updated by every run.