CI: enable new packaging tests using apkg
In order to solve #612 (closed):
- remove
tests/packaging
based ondocker
/py.test
and ever-present.packaging
- a total of 178 files / 1600 lines that achieved very little in an extremely redundant way - remove
distro/packaging
based onvagrant
/ansible
(65 files / 800 lines) - remove
pkgtest
using OBS from.gitlab.yml
- replace all above with a
pkg
stage usingapkg
For each supported distro, build and install packages and run packaging tests:
apkg install --build-dep
apkg test --test-dep
This is using new apkg LXC images based on lxc-gitlab-runner.
TODO
-
prepare apkg LXC images for all currently supported distros -
enable correct Knot DNS/build deps repos (probably script using python-distro
which is already required byapkg
)
Merge request reports
Activity
added packaging refactoring tests labels
added 14 commits
-
2c0f3483...ef24b152 - 10 commits from branch
manager
- 384864e1 - tests: remove tests/packaging
- 08b77d9a - tests: remove distro/tests
- e140dd46 - CI: disable OBS pkgtest
- bbec8667 - WiP: CI: enable new packaging tests using apkg
Toggle commit list-
2c0f3483...ef24b152 - 10 commits from branch
added 2 commits
added 2 commits
added 2 commits
added 1 commit
- e0df6a87 - manager: supervisord sd_notify extension: removed assert in favour of an explicit if
added 1 commit
- 92dd6047 - manager: supervisord sd_notify extension: removed assert in favor of an explicit if
added 1 commit
- a786b1f8 - CI: remove old distros unsupported by manager
I'm afraid the SUSE panic caused by
knot-dnssecutils
package split will need an additional command line option tozypper
added inapkg
.I wouldn't block this MR because of SUSE being special as always - I've marked the job with
allow_failure: true
for now until this is resolved.Edited by Jakub Ružičkamentioned in issue packaging/apkg#80
added 1 commit
- e440f828 - manager: removed specific versions of libraries from dependency list
mentioned in commit d9efe3b3
mentioned in issue #612 (closed)
mentioned in issue #610 (closed)
- Resolved by Vladimír Čunát
I saw
pkg:make-archive:
run on docker in the CI with an LXC image. While it may work fine, it seems like it was intended to specifytags
and putlxc
in there.I wonder if there's a way to get a warning when
tags
are missing or underspecified, as some properties don't make sense being assigned non-deterministically every time (e.g. amd64 vs. arm64, lxc vs. docker).
mentioned in commit 0376c96a
mentioned in merge request !1354 (merged)
mentioned in commit ec1e352b