Unfortunately the `latest` tag is amd64 only right now,
even though it did have both recently. I hope this will work reliably.

It looks like downloads won't work anymore:
 https://gitlab.nic.cz/knot/knot-resolver/-/jobs/890201
 https://gitlab.nic.cz/knot/knot-resolver/-/jobs/890312
which is probably because long-term support ended last summer.

These packaging tests are dying anyway;
the manager branch reworked them.
So at least the breakages won't be shown in red until then.

https://gitlab.nic.cz/knot/knot-resolver/-/jobs/852665
https://build.opensuse.org/request/show/1050454

obs:leap15 after updating fails later in the vagrant step though:
https://gitlab.nic.cz/knot/knot-resolver/-/jobs/852799

We're usually not interested in CI on older commits,
and this default will help cancelling expensive respdiff jobs.

Also add default runner tags to make them less likely
to get underspecified.  For example, each job should choose
one option in the docker/lxc and amd64/arm64 pairs.

https://gitlab.nic.cz/knot/knot-resolver/-/jobs/802541#L272

This reverts commit ac3e7ac7.
They have been fixed and seem reliable now.

It broke down and it isn't relevant anymore.

We've been unable to progress with these failures for some time,
and it's not good to have them red in CI all the time.
Manual start should allow easier testing of future fixes,
without doing the futile runs automatically.

Other pkgtest jobs can't do this, as they're designed for LXC
and we don't have an arm+LXC runner.

The apkg installation through pip3 was pulling too new jinja2 version,
breaking subsequent usage of sphinx to build docs (in `apkg build`).

We don't need this on the versions before nix 2.4,
but let's switch now already.

Vladimír Čunát authored 3 years ago and Tomas Krizek committed 3 years ago

For now just a simple docker-based build, atop nixos-unstable
(for now my nixpkgs branch that also adds apkg itself).

The child pipelines behave a bit differently than expected,
in this respect.