Closed 2asoft closed 4 years ago
What CI do you think we can use?
The repo will remain closed, thus services like TravisCI will require a paid account.
Github Actions is interesting, but I don't know how the pricing works for it.
For Windows builds, there is almost only AppVeyor, which is indeed paid for closed-source projects.
https://azure.microsoft.com/en-us/pricing/details/devops/azure-devops-services/ We may be able to use this for Windows builds though. 1800 minutes per month is better than nothing =)
Windows+MinGW can be compiled with Linux+MinGW (cross-compilation for Windows). But I'd prefer to have a "native" Windows build, of course.
Project must build for all of the following targets (more may be added in the future):
A quick exploration of CI tooling. List taken from wikipedia and each item briefly explored.
29$/mo cheapest
Self-hosted unlimited-minutes agent requires custom set up(locally or on a VPS, etc)
paid for closed
cheapest paid plan 75$/mo: 20 projects, 10 GB cache storage, 3 GB RAM & 2 vCPU
paid cheapest 2995$/year, seems self-hosted too
cheapest 10$/mo for 1300 minutes
63$/mo cheapest
beta of hosted requires sign up, requirements/availability unclear
Some of these are not free for private repos, which rules them out for now. All self-hosted options are not considered currently due to lack of any infrastructure to set them up, and belief that hosted options should cover the current needs. GitLab is ruled out because we are currently not interested in moving to it.
Self-hosted unlimited-minutes agent requires custom set up(locally or on a VPS, etc)
cheapest paid plan 75$/mo: 20 projects, 10 GB cache storage, 3 GB RAM & 2 vCPU
Of these options, GitHub actions and Azure DevOps appear to be most suitable. GitHub Actions does not require additional accounts and any other setup(except the actions, of course), and is the first choice. Azure DevOps is second choice, and will be explored if GitHub Actions is for any reason insufficient.