ContainerImages/gasket-driver/pipeline/head Something is wrong with the build of this commitDetails
Most of the time, we want to build the module for the latest version in
the *testing* stream, so that it will be ready when that version moves
to *stable*. There may be cases, though, where we need to build for a
different stream. For example, if the module never built successfully
by the time a version moved from *testing* to *stable*, we may need to
manually build it for the current *stable*.
ContainerImages/gasket-driver/pipeline/head There was a failure building this commitDetails
Apparently, the stream JSON file on the Fedora CoreOS website gets
updated on the same day the release is made. If Zincati checks for and
applies the update on the NVR machine before Jenkins has built the
_gasket_driver_ container image, Frigate will fail to start.
It seems like the *testing* stream tends to contain the same packages as
the *stable* stream, but released one cycle ahead. Thus, the kernel
package in one week's *testing* will be the same package in the
following week's *stable*. We should be able to stay ahead of Zincati
on the NVR machine, therefore, if we build the driver for the *testing*
stream.
ContainerImages/gasket-driver/pipeline/head There was a failure building this commitDetails
This Jenkins pipeline runs every day and fetches the latest FCOS
metadata to determine if a new version of the kernel driver needs to be
built. If no container image matching the kernel version in the latest
FCOS release exists, it will be built and pushed to the image
repository.
Dustin