Access to last commit and pull requests CI build artifacts

[Ale Martinez - No direct email please]

Each push to master and pull request on https://github.com/GoldenCheetah/GoldenCheetah generates an automatic build on Travis-ci for macOS/Linux and on AppVeyor for Windows.

Master builds are fully functional like snapshots and dev builds, which are generated by the same scripts, the builds can be accessed following the corresponding links on main page:

Pull request builds are similar, but have no access to online service since they don't include the required secrets for security reasons, the builds can be accessed following the Details link on each pull request:

On AppVeyor there is an Artifacts tab to download the Windows installer.

Travis has not such service so macOS and Linux builds are uploaded to free.keep.sh and the download links are available at the end of build logs (beware to expand the after_success script result) and they are valid for 24hr.

Hope this helps with testing of new features.

Cheers, Ale

[Ale Martinez]

Since it seems to be some confusion, it is necessary to remark 2 limitations of Pull Request builds:

1) They are not verified in any way by GoldenCheetah team, so please review the source code modifications before to use any binary build from them.

2) They don't include the secrets required to access online services s.t. Strava, Withings, etc.

Builds from master push have none of this limitations and they are eventually promoted to snapshot builds first and dev build later once they have endured more testing.

In short, the risk of using master build is uncovered bugs but pull request builds may pose security risks, be careful.

[Ale Martinez]

Due to travis-ci.org decommision we migrated to travis-ci.com, regrettably build credits are limited there and we had to disable PR builds and build from master pushes other than those used to generate binaries.

Contributors building on Windows only, willing to test their code on macOS/Linux which is highly recommended, need to create a free account on travis-ci.com to enable ci builds on their forks and to add [publish binaries] to the commit message.

[Ale Martinez]

On march 31 Travis-ci disabled macOS build environment so I migrated macOS builds to AppVeyor, it was easier than I anticipated so also added Linux build and now we have Windows, macOS and Linux builds available as described above for each push to master and PR again.