On 02/26/2010 01:23 PM, Doug Reiland wrote:
Thanks for both of you for these details.
By "serialized", I mean non-parallel package builds because of the
waitrepos.
Can host.capacity be changed on the fly (pop into psql while stuff is
running)? If not, how well does the system handle a kojid stop with a
bunch of outstanding work?
/etc/init.d/kojid stop
change capacity
/etc/init.d/kojid start
and outstanding tasks are handled cleanly.
waitRepo is a special task; In my experience, if there is no version of
the repository yet, a task against a build root will automatically have
a waitRepo task (before even adding the buildArch tasks to the task queue).
You can add a waitRepo task to a build task on a per-build basis, either
through the command-line (koji wait-repo iirc), and possibly as an
option to the "koji build <options> <tag> (...)" command as well
(have
no experience with such).
-- Jeroen