Squads are running into issues with builds now that Travis has put limits on number of builds.
From what I’ve heard:
- Bamboo – self-hosted with unlimited usage and provides a centralized dashboard, but not trusted as reliable as builds sometime fail for mysterious reasons
- Travis – was popular, but now applying monthly limit [ref]
- GitHub Actions – some groups are experimenting with these as an alternative to Travis; however, these are limited to 2000 minutes/month [ref].
- Azure Pipelines – allows 1800 minutes/month (maybe unlimited… wording isn’t exactly clear) for open source with unlimited for self-hosted CD/CI [ref]
I believe @jdick & @ibacher have written to Travis asking for OSS credits; I’ve just emailed Travis support from our infrastructure email account as well, hoping we might be able to get OSS credits and avoid having to shift all Travis builds elsewhere.
I believe the draw of Travis or GitHub Actions is being able to manage them using GitHub credentials, their reliability, and the ease of creating them.
For devs, are there reasons other than reliability to avoid using our Bamboo CI?
@cintiadr, I believe the reliability issues on Bamboo are primarily due to (1) depending on jobs to clean up after themselves and (2) caches filling up disk space. Would it be possible to improve Bamboo reliability by isolating these builds (via Docker and/or by automatically building & destroying Bamboo agents)?
Lastly, is there any way for us to estimate our CI build usage (e.g., minutes/month)? I realize our builds are mostly happening across Travis-CI (.org ± .com) and Bamboo at the moment. Does anyone know if there’s a way to estimate our typical build time in minutes/month from either of these environments?