LLVM Snapshots are built fresh in daily new incubator projects such as `@fedora-llvm-team/llvm-snapshots-incubator-20231107` and the regex wouldn't match them before.
Now the regex works good with grep in the following scenarios:
```
$ echo "@fedora-llvm-team/llvm-snapshots/fedora-rawhide-x86_64/llvm" | grep -ioP '@fedora-llvm-team/llvm-snapshots[^/]*/.*x86_64/(llvm|clang)'
$ echo "@fedora-llvm-team/llvm-snapshots-incubator-20231107/fedora-rawhide-x86_64/llvm" | grep -ioP '@fedora-llvm-team/llvm-snapshots[^/]*/.*x86_64/(llvm|clang)'
```
See https://pagure.io/releng/issue/11664 for more info.
Basically createrepo_c in f39+ will not work for making epel7 updates,
so we need to wait until it goes EOL before upgrading here.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
Turns out back in 2015 (in 623be6ff73) I added a robots.txt on the koji
hubs to disallow crawling, but since it's behind the proxies, no one
ever saw that robots.txt. Instead they got the default one that just had
a 'crawl-delay 1' in it.
So, lets tell robots to go away for real now, as they are causing load
problems on the koji database and I don't think it's particularly useful
for koji to be indexed. It's a lot of dynamic content anyhow.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
We want to get core dumps from these builders in order to try and track
down livemedia failures in python with SIGILL.
https://bugzilla.redhat.com/show_bug.cgi?id=2247319
We just enable this on those builders for now and we set it so it is the
limit for the systemd-nspawn containers that mock uses.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
f39 adds flatpaks for ppc64le, so we need to allow ppc64le builders to
access the registry directly so they can install flatpaks in the ostree
install images. Without this they try and get them from the cdn and the
builder firewall blocks them and it times out and the image fails to
compose.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
We aren't using this box and there's a use for it in the CentOS side, so
we are going to hand it over there. :)
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
It's overall simpler and more idempotent to just use a side repo
maintained outside of ansible than re-create one on each system
on each run of the plays.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
This still doesn't mean that one project (= sandbox) can waste that
many workers, we still keep the per/sandbox limit on 35. This change
though drastically helps Packit which serves many users under a single
owner (but multiple sandboxes).
