On Sun, Aug 6, 2017 at 7:19 AM, Aleix Pol <aleix...@kde.org> wrote: > On Sat, Aug 5, 2017 at 8:26 PM, Ben Cooksley <bcooks...@kde.org> wrote: >> On Sun, Aug 6, 2017 at 4:02 AM, Aleix Pol <aleix...@kde.org> wrote: >>> On Sat, Aug 5, 2017 at 9:44 AM, Ben Cooksley <bcooks...@kde.org> wrote: >>>> On Sat, Aug 5, 2017 at 11:42 AM, Aleix Pol <aleix...@kde.org> wrote: >>>>> Hey, >>>> >>>> Hi Aleix, >>>> >>>>> Just configured to have the server issue a new daily build (at 3am >>>>> UTC, if I cron'ed correctly). Shouldn't be a big strain on the server >>>>> and will be more useful to developers who are trying to make sure that >>>>> their application works. >>>> >>>> I can confirm that the time the cronjob is set to run is 3am. >>>> That's fine from my perspective (it's basically what the system is >>>> meant for) - I assume it'll be finished by approximately 10am? (which >>>> is when LXR starts it's KF5 update) >>>> >>>>> >>>>> Logs can be found here: >>>>> https://distribute.kde.org/flatpak-apps-testing/log-flatpak-kde-applications.text >>>>> >>>>> Cheers! >>>>> Aleix >>>> >>>> Cheers, >>>> Ben >>> >>> Yes, it should be done in 7h. >> >> Perfect. >> >> At some point we should probably connect this with >> binary-factory.kde.org so instead of rebuilding everything we can >> rebuild just what's changed, unless you're already doing incrementals. > > Flatpak is pretty smart at not rebuilding what didn't change: checks > whether the dependencies or the repository changed, has ccache > integrated by default.
Awesome. In case anyone is wondering, some systems like api.kde.org for instance don't do this (something we need to fix) > > Aleix Cheers, Ben
