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>
Grouping compose changes per Fedora version will allow
us to retrigger the builds separately in case of failure.
Signed-off-by: Miguel Martín <mmartinv@redhat.com>
According to the documentation 'build' can be used after 'major', 'minor'
and 'patch' have been already used and a fourth version part is needed.
On the other hand, it's only mandatory to use at least one of 'major',
'minor' or 'patch'.
We are using 'patch' and 'build' in compose-images so this change is
to make the versioning consistent among both projects.
Signed-off-by: Miguel Martín <mmartinv@redhat.com>
Remove 'baseBranches' configuration option as it's not allowed
within the regex customManager.
Fixes#59
Signed-off-by: Miguel Martín <mmartinv@redhat.com>
I noticed we weren't getting updates and I think the
core problem here is renovate was only triggering on
the devel compose. But we just "floated" to whatever
was found in the production compose as a base.
Also we had a random copr.
Drop that stuff, and just pin on the production compose.
In order to streamline the focus, let's drop fedora-bootc:eln.
- We want to be moving container builds into upstream distributions anyways
- Building two containers from one git repository is awkward in Tekton
