search

owncloud / client

🖥️ Desktop Syncing Client for ownCloud
GNU General Public License v2.0
1.4k stars 665 forks source link

Setup our own Craft cache (mirror) #6619

Closed dschmidt closed 6 years ago

dschmidt commented 6 years ago

Our AppVeyor builds start to fail whenever the cache name changes on the KDE Mirrors because we then try to build all deps ourselves in AppVeyor which then times out. Moreover it helps us being able to update docker images after the cache has been removed from KDE mirrors. Current issue: KDE removed the cache for Qt 5.10 builds and we need to switch to 5.11 because I need changes in the docker image.

We do not need to build any packages for the cache for now, we should simply mirror the KDE mirror and make sure that old caches are not deleted.

http://ftp.acc.umu.se/mirror/kde.org/files/craft/master/ I use this mirror as it turned out to be more reliable/faster than https://files.kde.org/craft/master/

We need that on a public webserver (for AppVeyor to access).

Bonus points if our script/job sets up a "latest" link, so we can use that cache version in master.

We should then also add a todo item for creating release branches, that then pins the qt version to whatever we use for the release. We can possibly use that information at some point to update docker images for that specific branch.

guruz commented 6 years ago

So client 2.5.0 on Windows (only there) will have Qt 5.11.x? Which one of those?

dschmidt commented 6 years ago

If there are strong reasons to go back to 5.10, I can possibly make that happen - but it would be quite some effort :-(

So yes, I would prefer to go with Qt 5.11. Craft currently provides Qt 5.11.0. @TheOneRing can we get Qt 5.11.1?

dschmidt commented 6 years ago

Talked to @TheOneRing on IRC. The cache is still named Qt 5.11.0 but already contains 5.11.1. So yes, we would have Qt 5.11.1 for 2.5.

guruz commented 6 years ago

@dschmidt We definitely need the .1 because of https://github.com/owncloud/client/issues/6517#issuecomment-398021244

dschmidt commented 6 years ago

@guruz Not really, that issue is about 2.4.x, which we still build with Qt 5.6.2 for Windows. master/2.5 does not use it anymore anyway.

dschmidt commented 6 years ago

and since https://github.com/owncloud/client/pull/6620 the crashreporter does not need it either ;-)

jnweiger commented 6 years ago

done: https://download.owncloud.org/mirror/craft/


$ du -sh Qt_5.11.1/windows/msvc2017_*
1,4G Qt_5.11.1/windows/msvc2017_32
1,7G Qt_5.11.1/windows/msvc2017_64
dschmidt commented 6 years ago

I'm currently testing it...

dschmidt commented 6 years ago

Works!