The relevant parts were made conditional and only applied in the staging
environment, change that. Alongside, ensure the obsolete hub plugin
package and plugin configuration files are removed and don't
automatically update any of the involved packages.
Signed-off-by: Nils Philippsen <nils@redhat.com>
This is the threads that are doing deletes of repos. Since we have so
many repos, lets increase the delete threads as well so it can hopefully
keep up.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
We had a patched version, but the patches have been merged upstream so
we should switch back to using the 'stock' kojira.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
See https://pagure.io/releng/issue/9746
It's desired to have a src repo for eln-build so queries can be done
against it. This enables this for eln-build. If it turns out to cause
too many problems we can disable it again.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
Turns out fwupd needs to also be signed right for secure-boot, so we
should add it to the list of packages in koji that needs the secure-boot
permission. This should prevent provenpackagers from building it and
pushing out an inoperative one.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
One of the 2 patches we were carrying for kojira was merged upstream in
1.22. The other wasn't yet, so we need to keep it around for now.
But we need to merge in the other 1.22 changes or auth fails.
Hopefully this rebases to 1.22
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
Upstream switched from python-requests-kerberos to
python-requests-gssapi and dropped some options.
Unfortunately, these cause kojid / kojira to not even start if they are
present, so we have to remove them to make things happy.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
The s390x boxes have been really slow of late and have i/o issues.
Lets make sure that we only use x86 and ppc64le hosts for this so to
avoid moving large srpms around.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
This will mean that anything we don't have a policy for will be denied
instead of allowed. We want this (safer) default.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
New versions of kojira can optionally produce a queue file.
This shows the buildroots that it knows need regeneration and
how long they have been known out of date. It might help users
see where a buildroot they are waiting for is in the queue.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
This only works currently for aarch64. we have 2 buildhw's that have a
lot of resources for aarch64, except for disk, so they are great fast
heavy builders. All the other arches machines are pretty much all the
same, so this doesn't help on any of them.
We might someday expand this to more arches and packages when it makes
sense to.
In this case it takes a chromium build that takes ~24 hours
down to taking about an hour.
Note that we are currently keeping these in the default channel too so
they can do normal builds most of the time. That might make chromium
wait a bit, but still will end up being a LOT faster.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
The stock 1.21.1 kojira has a number of problems.
It only does deletes rarely as part of the main thread, so if you are
needing to delete a ton of old repos it will never get to them all.
Also, it checks for it's running newrepos at a place in the loop that
causes it to take a lot longer to notice when it's hit the max for
newrepos.
So, this is the 1.21.1 version, and we will check in the diff/hotfix
which is upstream head version + several patches.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
