Today jlanda, austinpowered and mizdebsk discussed about ticket
https://pagure.io/fedora-infrastructure/issue/8157 in #fedora-admin and
came up with a few questions on how to implement that solution that I think
would be nice to share with the wider group.
There are basically 2 possibility :
1 - We run ansible-report as a pre-commit hook
This means that ansible-report will be run locally before a contributor
commit a change. This is not ideal since our contributor are running all
kind systems (rhel, fedora, windows ?) so having something that work well
for everyone will not be simple. Also this forces our contributors to
install ansible-report locally.
2 - We run ansible-report as a pre-receive hook
This means that ansible-report is run on batcave01, but we cannot run
ansible-report just on a commit, we need to run the tool against the full
repository every time. That involve making a clone of the repo applying the
changes in the incoming commit, then run ansible-report on that repository.
This has also a few disadvantages, first we first need to clear all the
errors reported by ansible-report in our repo before we enable the hook
otherwise all commits will be rejected. It will also slows down every
pushes (time to clone, apply patch, run the tool).
Do people have other ideas ? Is this change worth the trouble ?
we are now in the infrastructure freeze leading up to the Fedora 31
Final release. This is a final release freeze.
We do this to ensure that our infrastructure is stable and ready to
release the Fedora 31 when it's available.
You can see a list of hosts that do not freeze by checking out the
ansible repo and running the freezelist script:
ansible/scripts/freezelist -i inventory
Any hosts listed as freezes is frozen until 2019-10-22 (or later if
release slips). Frozen hosts should have no changes made to them without
a sign-off on the change from at least 2 sysadmin-main or rel-eng
members, along with (in most cases) a patch of the exact change to be
made to this list.
You are kindly invited to the meeting:
Fedora Infrastructure on 2019-10-31 from 15:00:00 to 16:00:00 UTC
The meeting will be about:
Weekly Fedora Infrastructure meeting. See infrastructure list for agenda a day before.
[PATCH 1/2] bodhi-pungi: F32 will be the next "branched"
[PATCH 2/2] bodhi-pungi: enable aarch64 and ppc64le for silverblue
Now that F31 is a go we need to do a few things. One of them
is enabling other architectures, which was done in rawhide and f31.
This propagates it into bodhi.
In order to fix issue 8322  python2-koji-sidetag-plugin-hub needs
to be updated. This would be done with the following commands:
$ koji move epel7-infra-stg epel7-infra koji-sidetag-plugin-0.1-2.el7.infra
[root@batcave01]# ansible koji -m package -a
'name=python2-koji-sidetag-plugin-hub state=latest update_cache=yes
[root@batcave01]# ansible koji -m service -a 'name=httpd state=reloaded'