Mailinglist Archive: opensuse-buildservice (312 mails)
| < Previous | Next > |
Re: [opensuse-buildservice] BS monitor does not show all scheduled jobs
- From: <doiggl@xxxxxxxxxxxxxxxxxx>
- Date: Fri, 31 Jul 2009 19:39:22 +1000
- Message-id: <674580bb0c949eff789615430df8ed36@xxxxxxxxxxxxxxxxxxxxxxx>
Hello
Thanks Dominique, is there any possibility of utilizing the idle hosts to
help out even though it is a different platform e.g ppc64 [37 out of 197]
https://build.opensuse.org/monitor
Cheers Glenn
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx
Thanks Dominique, is there any possibility of utilizing the idle hosts to
help out even though it is a different platform e.g ppc64 [37 out of 197]
https://build.opensuse.org/monitor
Cheers Glenn
Dominique wroteto
The only way to reduce the waiting time is throwing more build power at
it.
If you have 200 packages, each taking 30 minutes to compile, it's going
take 100 hours, no matter in what order you build them.throw
Except in the rare case that all packages are waiting for a single build
(example gcc). But then, this also won't change, as it would block
everything else, anyhow it's 'the only' possibility to start with, as
everything is blocked.
So in short: I guess to get shorter cycles, just more build hosts need to
be connected. (which of course summarizes down to somebody needing to
money in).on
A 'distributed' approach might be interesting, but I understand that the
question of trusting RPMs built in such a way would be very very high up
the list (no guarantee a remote worker is not tampering the createdRPMs).
Dominique
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx
| < Previous | Next > |