[clashmeifyoucan]

I'm wondering if there's still a solid reason to use Travis for new projects. I can't be bothered to move my current builds from there to GitHub Actions, but for future projects GitHub Actions seems way more lucrative to use. I think both pale out in comparison to GitLab CI however, it's a pity GitLab is less popular.

[Master_Odin]

Not really, and hasn't been for a while, assuming your hosting your code on GitHub or GitLab. Both offer a service that is comparable to Travis, and are much better backed at this point after the acquisition of Travis and gutting of their staff.

The only thing I sometimes miss from Travis was the ability to run "debug" builds, but most of the time this was necessarily only because of how omnibus their VMs were and oddities of pathing.

[softinio]

I like Gitlab and I tried them for a year before moving off of their CI couple of years back. Main reason was their CI was slow and had some reliability problems at the time. Hopefully they have resolved those by now as I would like to see more adoption of their service for sure. Will give them another shot soon :-)

[clashmeifyoucan]

I recently found a comparison¹ which was interesting. Of course, it's gitlab's so take that as you will.

[1] https://about.gitlab.com/devops-tools/github-vs-gitlab/#comp...

[sytse]

Deeplink to the GitHub Actions vs. GitLab CI part of the decision kit https://about.gitlab.com/devops-tools/github-vs-gitlab/ci-mi...