Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doc: mention powerful builders disk space and admin how to #3505

Merged
merged 1 commit into from
Nov 5, 2024
Merged

doc: mention powerful builders disk space and admin how to #3505

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion doc/user_documentation/powerful_builders.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,8 @@ Pros & Cons of *high-performance builders*
Once you get them, the *high-performance builders* will handle your builds much
faster. According to the specification as of October 2023, they are
approximately 8 times faster than the *normal builders*, but the actual speedup
is very task-dependent.
is very task-dependent. They also provide twice as much disk space (280G vs
regular 140G).

The downside is that they are in limited supply. If other users request them at
the same time as you, you'll compete with others, and you may spend a bit longer
Expand Down Expand Up @@ -51,3 +52,9 @@ is basically a Python regexp in a format ``owner/project/chroot/package``, e.g.

.. _Blink: https://en.wikipedia.org/wiki/Blink_(browser_engine)
.. _issue: https://github.com/fedora-copr/copr/issues

Admin SOP
---------

Copr maintainers can configure high performance builders through the
``EXTRA_BUILDCHROOT_TAGS`` variable in ``/etc/copr/copr.conf``.