kind-ci / containerd-nightlies Goto Github PK

containerd/containerd#7369

we can use .github/workflows/nightly.yml GO_VERSION: '1.19.1'

(we don't use upstream nightly builds still because they're harder to automatically consume, with paths like https://github.com/containerd/containerd/suites/8409151131/artifacts/371863559 => latest linux amd64 nightly build in a zip, and release builds)

we might be able to switch to upstream for release versions though and lately we're shipping those more often than early tags, however in the past we needed to pick up fixes ASAP so it's probably still worth maintaining here

cc @aojea

instead of getting a failure message, let's detect early that the tag already was published and skip the build

cc @aojea

minor but we should fix this so it's easier to check the health of the pipeline at a glance instead of comparing releases to what exists in containerd
cc @aojea

This version detection logic is not robust.
As the result, https://github.com/kind-ci/containerd-nightlies/releases/tag/containerd-1.5.1 was released with an unexpected version of runc (expected: rc94, actual: rc93).

The right way is to read script/setup/runc-version.

https://github.com/containerd/containerd/blob/v1.4.5/script/setup/runc-version
https://github.com/containerd/containerd/blob/v1.5.1/script/setup/runc-version