NextCloud clients are not built on a daily or weekly basis
There are daily builds of the server and the Android client, but there are no regular builds of the desktop clients.
The current Mac release was built on 2016-10-3, which makes it a few days newer than the "prerelease" dated 2016-9-30.
The lack of regular builds is impacting users who cannot use outdated SSL/TLS protocols (see nextcloud/client_theming#64) and other bugs where a simple updating of the package based on the latest ownCloud client would fix the issue.
Acceptance criteria for this bug is an automated process to produce:
- [ ] Daily or Weekly builds of the Mac client
- [ ] Daily or Weekly builds of the Windows client
- [ ] Daily or Weekly builds of a Debian desktop package (.deb)
- [ ] Daily or Weekly builds of a Fedora desktop package (.rpm)
- [x] Continuous builds of an AppImage for most Linux distributions
There are continuous AppImage builds for each git push.
Download links are in each Travis CI build log. The most current one is https://transfer.sh/5fm9D/nextcloud-desktop-sync-client-gita4d5009-glibc2.14-x86-64.appimage
Is the blocker on this issue time or hardware?
@jlfranklin Time I'd say. But there are no reason for it as the builds are done on every single commit.
Really? Where are they? Last commit to this repo was four days ago. Where is the Mac client built for that commit?
Sorry, what I meant what the snap, and the Linux package. Though the snap should work on Mac as well. Have you tried?
Snap does not work on macOS, it is for Ubuntu. AppImage runs on almost all Linux distributions. The latest one was built 2 days ago, as we can see from the Travis CI build log. It can be downloaded from https://transfer.sh/DcAcJ/Nextcloud_desktop_sync_client_-git0e6c5eb-glibc2.14.glibc2.14-x86_64.AppImage.
Snap does not work on macOS
I might be wrong. cc'ing @3v1n0 on this... --^
Not yet... :-)
Anyway you guys should really upload the snap in the store, it will really take few minutes. And so for daily-builds.
Daily or weekly builds are more useful here because this repo only covers the theming for the client. The guts of the client is in owncloud/client. Unless a change in the upstream client repo triggers a rebuild, we will need a schedule or some other trigger.
Travis CI supports cron now. https://blog.travis-ci.com/2016-12-06-the-crons-are-here I think this would be suitable here.
Travis CI also has an OS X build environment. https://docs.travis-ci.com/user/osx-ci-environment/#OS-X-Version
Their Windows build environment is still a WIP: travis-ci/travis-ci#2104