Hi
First, thanks for copr and to all who built and maintain it. It is excellent and now my preferred way of building RPMs for free/libre/open source software.
Is there a way that long-running jobs (I'm thinking kernel, gcc etc) can be assigned to their own dedicated build servers? The packages I build are usually quick (a few minutes) but they sometimes have to wait a long time for these longer jobs to finish.
Failing that, is there a way to spin-up a private build server tied to my project?
Thanks!
Dne 30. 01. 19 v 12:22 harbottle napsal(a):
Is there a way that long-running jobs (I'm thinking kernel, gcc etc) can be assigned to their own dedicated build servers? The packages I build are usually quick (a few minutes) but they sometimes have to wait a long time for these longer jobs to finish.
Currently one user can build only 6 concurent builds at the same time. So someone submit 60 kernels it will not eat whole pool and you should build your small packages. If *you* submit 60 kernel and at the same time you want to build some small package in mean time, then you can lowe priority of those long running jobs (before you submit them):
copr build --background kernel.src.rpm
Failing that, is there a way to spin-up a private build server tied to my project?
Nope. There are some talk around this idea, but it was never implemented.
Miroslav
On Thursday, January 31, 2019 12:31 PM, Miroslav Suchý msuchy@redhat.com wrote:
Currently one user can build only 6 concurent builds at the same time. So someone submit 60 kernels it will not eat whole pool and you should build your small packages.
"livegrenier/acs-kernel" currently has 10 concurrent multi-hour kernel builds running...
copr-devel@lists.fedorahosted.org