See https://pagure.io/fedora-infrastructure/issue/12995
We want to be careful adding anything here, but the same reasons we add
chromium are in play here. There's no ppc64le or s390x builds, so it
will just affect aarch64 and x86_64 where we have a lot of hosts in
heavybuilder channel.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
This is part of an approved change [1] to remove `koji-osbuild` from
Fedora's Koji instances. In this commit the Koji configuration is
changed to no longer serve `osbuildImage` tasks in web or hub.
The `koji-osbuild` plugin has been replaced previously with the
`koji-image-builder` plugin which, instead of talking to a remotely
hosted service, builds images on Koji builders themselves.
All users of `koji-osbuild` have been migrated to `koji-image-builder`
and no builds are being scheduled that need to be handled by
`koji-osbuild` anymore.
[1]: https://fedoraproject.org/wiki/Changes/KojiServiceImageBuilderRemoval
Signed-off-by: Simon de Vlieger <supakeen@redhat.com>
We need to set this the same as the proxies so we don't have a keepalive
on the proxies that gets cut off my the lower limit on the hubs.
This may fix the 502 error with watch-tasks/watch-logs
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
This introduces a set of variables for managing infrastructure changes
as EPEL minor versions change over time. This should drastically
simplify our changes during EPEL mass branching. This also drops the
earlier attempt of EPELCycleNumber and EPELBootstrapNumber variables,
which are no longer used.
Signed-off-by: Carl George <carlwgeorge@gmail.com>
On riscv we don't want to do generic tasks that can be done on any arch
on riscv builders. We want those to go to the x86_64 builders that are
much faster.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
The riscv koji isn't using a seperate kojipkgs, so it's like staging and
should just serve repos/etc by itself.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
Enables the `image-builder` plugin from `koji-image-builder` in the
production environment for both the koji hub, and the koji builder
(kojid).
This is based on the earlier enablement in staging where I've
succesfully tested some builds and it didn't seem to bring down all of
the staging instance.
Signed-off-by: Simon de Vlieger <supakeen@redhat.com>
Enables the `image-builder` plugin from `koji-image-builder` in the
staging environment for both the koji hub, and the koji builder (kojid).
Signed-off-by: Simon de Vlieger <supakeen@redhat.com>
We want to add these releases as they happen so that koji-gc can
properly clean up builds signed by those keys.
I filed https://pagure.io/infra-docs-fpo/pull-request/367 to also update
the branching sop to do this.
This commit adds f42/43 here.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
Per https://pagure.io/infra-docs-fpo/pull-request/361 there seems
to be substantial confusion about what the "Frozen" variable
means: does it refer to the infrastructure freeze, or a freeze
for the pending release? It seems like @kevin thought about it
as referring to the former, but the only practical use of it in
this repo treats it as the latter.
Let's make this clear with explicitly-named variables.
InfraFrozen tracks the infrastructure freeze, NextReleaseFrozen
tracks freezes for the pending release. We formerly had a var
called RelEngFrozen which had a similar meaning, but I like this
name more because the freeze doesn't apply to *all* releng
operations - just because the current Branched is frozen doesn't
mean Rawhide or stable releases are frozen.
We keep Frozen for 'backwards compatibility', in case anyone is
referring to this variable from outside of the repo.
This goes along with https://pagure.io/infra-docs-fpo/pull-request/361
which updates the SOPs.
Signed-off-by: Adam Williamson <awilliam@redhat.com>
Removing the topic_prefix from fedora messaging config files was a bit
premature. So let's put them back in place.
Signed-off-by: Michal Konecny <mkonecny@redhat.com>
This will unify all the handlers to use first uppercase letter for
ansible-lint to stop complaining.
I went through all `notify:` occurrences and fixed them by running
```
set TEXT "text_to_replace"; set REPLACEMENT "replacement_text"; git grep
-rlz "$TEXT" . | xargs -0 sed -i "s/$TEXT/$REPLACEMENT/g"
```
Then I went through all the changes and removed the ones that wasn't
expected to be changed.
Fixes https://pagure.io/fedora-infrastructure/issue/12391
Signed-off-by: Michal Konecny <mkonecny@redhat.com>
Here's a pull request to setup a secondary riscv-koji hub.
There are still outstanding issues, but things should be
good enough to merge and deploy the initial instance and
interate from there. Also I plan to run a --check --diff to make sure
there's no changes on primary hubs/etc.
Signed-off-by: Kevin Fenzi <kevin@scrye.com>
