From: Igor Gnatenko <ignatenkobrain@xxxxxxxxxxxxxxxxx>
The 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 tak precedence over builds submitted by
MBS.
Signed-off-by: Igor Gnatenko <ignatenkobrain@xxxxxxxxxxxxxxxxx>
---
roles/mbs/common/templates/config.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/roles/mbs/common/templates/config.py b/roles/mbs/common/templates/config.py
index 8e5e86c..278c651 100644
--- a/roles/mbs/common/templates/config.py
+++ b/roles/mbs/common/templates/config.py
@@ -180,7 +180,7 @@ class ProdConfiguration(BaseConfiguration):
DEFAULT_DIST_TAG_PREFIX = 'module_'
# New name
- NUM_CONCURRENT_BUILDS = 20
+ NUM_CONCURRENT_BUILDS = 100
# Delete module-* targets one hour after build
KOJI_TARGET_DELETE_TIME = 3600
--
2.21.0
_______________________________________________
infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
