I would like to propose increasing NUM_CONCURRENT_BUILDS for MBS to
value 100 after beta freeze is over.
The above MBS setting controls how many parallel component builds MBS
can run at the same time. Current value is only 20. That value was
defined 3 years ago, in March 2017 when there were much fewer modules
in Fedora. Our Koji has capacity to run many more builds. Currently we
have 158 Koji builders in default channel that are able to run RPM
builds. Their total capacity is 566. Therefore it should be safe to
increase MBS NUM_CONCURRENT_BUILDS to at least 100. Especially since
Koji builds submitted by MBS have lower priority than default for
non-modular component builds submitted by packagers, so
packager-submitted builds will take precedence over builds submitted
The Bodhi frontend container was not rebuilt when the Fedora 30
configurations were added to production.ini. This means that the
frontend is not aware of the policy of 3 days to stable, while the
backend is aware. This means that the backend is adding comments to
updates to tell packagers they can push their packages, but the
frontend is not allowing them to push the packages.
To fix this, I will run this command:
$ sudo rbac-playbook openshift-apps/bodhi.yml
I will also send a patch to the releng SOP which doesn't explicitly
mention this step - it really should just link to the Bodhi SOP where
this is mentioned.
Hey, I just noticed that, while we have zchunked metadata for the F30
base repository, it's not enabled to for updates-testing.
I've looked in the ansible repo and in pungi, but I can't see where
createrepo_c is actually called for updates-testing. Can someone
please point me in the right direction?
First, I don't mean to point to anyone specifically here, but I just
wanted to send a reminder about some things:
1. For ansible commit messages, could everyone try and do:
area/thing/host: short synopsis of the change
Longer explanation of the change.
I realize it's anoying when just fixing a syntax error from a previous
commit or something, but when looking back at commit history it's really
a lot nicer to see:
src.fedoraproject.org: fixing a typo in previous commit, Z should be Q
I realize it's fun to add amusing log entries, but I have had to look at
git commit logs and it really makes it anoying to tell when something
was done unless it's nice and clear. Feel free to add your funny line in
the longer comment. :)
2. We are in freeze, so please get freeze breaks for any frozen hosts.
Of course if something is down/on fire you can push the fix and then go
back and make sure it gets approved. This will get a bunch easier when
we have ansible repo in pagure.
3. Finally: hotfixes. We have a process for these... I don't know if
it's too much of a pain or what, but it seems like sometimes we just
don't use it. The basic process is:
* add ansible play to copy files from our repo to the filesystem
* commit all the files you are going to touch.
* commit in a second commit the changes for the hotfix.
* push both with a comment about it.
* run playbook.
Perhaps we could make this easier with a ansible hotfix role that
already had all the ansible side and you just needed to commit the files
and diffs? in any case, it makes my teeth itch when running ansible or
applying updates drops a hotfix.
Thanks and I return you to your wed. :)
This leads to some exception being raised instead of by-pass safely.
It was useful at some point because pagure would not log error to
its logs otherwise but Patrick has since fixed it and I believe it
may be triggering some errors now.
Signed-off-by: Pierre-Yves Chibon <pingou(a)pingoured.fr>
roles/pagure/frontend/templates/pagure.wsgi | 1 -
1 file changed, 1 deletion(-)
diff --git a/roles/pagure/frontend/templates/pagure.wsgi b/roles/pagure/frontend/templates/pagure.wsgi
index 7f327fd0e..75c6ef343 100644
@@ -27,4 +27,3 @@ os.environ['TEMP'] = '/srv/tmp/'
from pagure.flask_app import create_app
application = create_app()
-application.debug = True
I would like to know what do you think about using an opinionated code
formatter for our ansible repo ? I think this would help with
enforcing a common style and make our yaml files easier to read and
I have been looking at https://prettier.io/ which support yaml and I
ran it on the repo's playbooks directory (see attached patch). Most
of the changes are indentation but we could enforce more rules using
prettier's configuration options if we wish
Prettier looks quite cool but the only down side is that it is a
have used a container to run it on my laptop.
Anyway what do you think about it ? Does anybody knows an alternative
to prettier ?