Hello,
If we could set copr to do ccached builds ? , sometimes I prefer use local builds which use ccache , and after cache gcc compilation , I can improve build times in 10 times more or less ... i.e. ccache could be very useful when we are trying fix FTBFS packages, where things are broken in post stages of the builds .
Thanks,
Hi Sérgio,
On Saturday, October 13, 2018 7:12:04 PM CEST Sérgio Basto wrote:
If we could set copr to do ccached builds ? , sometimes I prefer use local builds which use ccache , and after cache gcc compilation , I can improve build times in 10 times more or less ...
the design of copr build system isn't really ready to have this implemented, namely for storing the caches. The builder machines (which do the mock build) are freshly started VMs.
i.e. ccache could be very useful when we are trying fix FTBFS packages, where things are broken in post stages of the builds .
It is definitely better to try local build if you debug some packaging issue. You can try 'copr-rpmbuild' package, or '/bin/copr mock-config' and then play with mock's ccache directly.
Pavel
Thanks,
Sérgio M. B. _______________________________________________ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave@lists.fedorahosted.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.o...
Dne 15.10.2018 v 12:46 Pavel Raiskup napsal(a):
the design of copr build system isn't really ready to have this implemented, namely for storing the caches. The builder machines (which do the mock build) are freshly started VMs.
+1 Additionally using ccache on shared system is security problem as you can easily alter the cache for some other user.
Miroslav
On Fri, Oct 19, 2018 at 9:56 AM Miroslav Suchý msuchy@redhat.com wrote:
Dne 15.10.2018 v 12:46 Pavel Raiskup napsal(a):
the design of copr build system isn't really ready to have this implemented, namely for storing the caches. The builder machines (which do the mock build) are freshly started VMs.
+1 Additionally using ccache on shared system is security problem as you can easily alter the cache for some other user.
What do you mean? We are re-using builder machines only for user that owns the machine (made the first build on it).
So if you chain one-after-another ten consecutive builds each one compiling that same package, this might be useful.
Copr team
Miroslav _______________________________________________ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave@lists.fedorahosted.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.o...
On Fri, 2018-10-19 at 10:16 +0200, Michal Novotny wrote:
On Fri, Oct 19, 2018 at 9:56 AM Miroslav Suchý msuchy@redhat.com wrote:
Dne 15.10.2018 v 12:46 Pavel Raiskup napsal(a):
the design of copr build system isn't really ready to have this implemented, namely for storing the caches. The builder machines (which do the mock build) are freshly started VMs.
+1 Additionally using ccache on shared system is security problem as you can easily alter the cache for some other user.
What do you mean? We are re-using builder machines only for user that owns the machine (made the first build on it).
yes, that's what I have in mind, the user has their own cache.
Thanks for all the answers
So if you chain one-after-another ten consecutive builds each one compiling that same package, this might be useful.
Copr team
Miroslav _______________________________________________ copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave@lists.fedorahosted .org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidel ines List Archives: https://lists.fedorahosted.org/archives/list/copr-de vel@lists.fedorahosted.org
copr-devel mailing list -- copr-devel@lists.fedorahosted.org To unsubscribe send an email to copr-devel-leave@lists.fedorahosted.o rg Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelin es List Archives: https://lists.fedorahosted.org/archives/list/copr-deve l@lists.fedorahosted.org
copr-devel@lists.fedorahosted.org
-
Michal Novotny -
Miroslav Suchý -
Pavel Raiskup -
Sérgio Basto