It comes down to how often you build, but I’ve been using AWS Amplify for CI/CD, and it’s been really awesome and simple to set up. You point it to your GitHub Repo, and you’re good to go. It works well for webapps.
CI/CD on a budget for open source projects
11–16 of 16 posts
Re: CI/CD on a budget for open source projects
#12Google is offering free fuzzing to large open source projects:
https://google.github.io/oss-fuzz/getting-started/accepting-...
Re: CI/CD on a budget for open source projects
#13You can do everything mentioned in the bullet points (CI service, test, build environment, docker image repository, code quality, coverage, metrics) except running the production code for free on Gitlab.com or self-hosted GitLab instance.
Edit. Serious question: why would you want to set up and maintain several different tools when you can have everything running in one place?
Re: CI/CD on a budget for open source projects
#14Google is offering free fuzzing to large open source projects: https://google.github.io/oss-fuzz/getting-started/accepting-...
The Internet offers free fuzzing to open ports j/k that actually looks useful ;)
Re: CI/CD on a budget for open source projects
#15I did something similar with a Flask server on EC2 that is updated on every push using Github Actions.
Re: CI/CD on a budget for open source projects
#16You can use Lambda for CI/CD and it will run on demand so you'll not be paying for it within free tier.