This consolidates the different CI builds on one platform that provides support for the major three operating systems we build on (Linux, Windows, MacOS). The nomenclature and syntax is a bit different but it has the same functionality.
This commit introduces the Linux and Windows based workflows. All the build artifacts can now be downloaded from [bintray](https://bintray.com/beta/#/boinc/boinc-ci?tab=files). The CI workflows run for every pull request, every merge into the master branch and every Sunday around 12:00 (GMT).
Every first Sunday in a month a cleanup Script is run to delete old artifacts from Bintray. Artifacts from closed/merged pull requests get deleted then. Artifacts from weekly builds and merges into the master branch older than 6 months get deleted too.
Co-authored-by: Vitalii Koshura <lestat.de.lionkur@gmail.com>
Change build with devenv to more common used msbuild
Change AppVeyor cache saving from zip to 7zip with maximal compression
Fixes#2620
Signed-off-by: Vitalii Koshura <lestat.de.lionkur@gmail.com>
The weekly cronjob on Travis CI will trigger a cleanup once a month which will delete artifacts from closed pull requests and weekly builds older than 6 months. The Windows artifacts on AppVeyor are automatically deleted after 6 months.
- Fix existing configuration of openssl and curl flag files for different Android configurations
- Make openssl and curl build more silent
This fixes#2927
Signed-off-by: Vitalii Koshura <lestat.de.lionkur@gmail.com>
Switch from date attribute to number attribute in order to get versions older than a specified date. This is a limitation of the API.
The cleanup_bintray.sh script needs to be run by the BOINC bintray maintainer. See comments in file on how to use this.
Attributes can be used to easily delete old versions. A script can check if a PR is closed and delete all versions for this PR on bintray. Or it could delete all versions older than a threshold.
Attribtes only need to be added once. Currently this is done in the Travis build because this is running for every PR.
Until there is a better mechanism to control deployments on AppVeyor a deployment will happen for every merge into master. This will prevent it from failing.
On AppVeyor the archiving is done in prepare stage because they have an artefact cache for pull requests already available. So I moved the 7z stuff to prepare_deployment.sh so it does the same as the bath file. Filenames do not match because uploading to bintray is done differently but theyhave the same structure when available on bintray..
Copy a weekly build from master to https://bintray.com/boinc/boinc-ci so it is available for testers. Only specified build artefacts are copied (see deploy/prepare_deploy.sh). The copy operation is triggered via a Travis CI cronjob or a pull request from within the BOINC/boinc gitub repository.
Pull requests from forks are ignored because they can not have access to the bintray API key, this is a security restriction enforced by Travis CI.
Tal Regev