Instead of crating MRs, renovate will:
- Create the branch, wait for test results
- Rebase it any time it gets out of date with the base branch
- Automerge the branch commit if it's:
(a) up-to-date with the base branch, and
(b) passing all tests
- As a backup, raise a PR only if either:
(a) tests fail, or
(b) tests remain pending for too long (default: 24 hours)
Resolves#62
Signed-off-by: Miguel Martín <mmartinv@redhat.com>
Changes in `bootc-base-imagectl` and `install-manifests` files
must trigger konflux builds for all the existing base images.
Also changes in "minimal" or "minimal-plus" must trigger konflux
builds in all the "standard" images.
Signed-off-by: Miguel Martín <mmartinv@redhat.com>
It's confusing right now how the manifest names differ across
fedora-bootc, centos-bootc and rhel-bootc. Both rhel-bootc and
centos-bootc only use "bare" names like `minimal`, and `standard`, while
fedora-bootc prefixes everything with `fedora-`.
For FCOS/SCOS/RHCOS, it would be beneficial to maintain the same naming
across all of those.
Let's just match the naming here to the "bare" version. But add symlinks
so that we don't break the old names (but note that being symlinks, they
will no longer show up in `bootc-base-imagectl list`).
An update of a compose image from a specific Fedora version
triggers at least 4 builds: 'minimal', 'minimal-plus', 'standard'
and 'iot'.
We usually have 2 compose images updates (Fedora 42 and Rawhide) per
day so up to 8 builds are triggered at the same time. As we don't seem
to have a lot of resources in the Konflux cluster this leads to
build failures because of timeouts (the default pipeline timeout is 1h).
This change tries to mitigate this until we get more resources in the
Konflux cluster.
Signed-off-by: Miguel Martín <mmartinv@redhat.com>
