Help people migrating from GitHub who currently use Travis CI
Travis CI: https://travis-ci.org/ is used by many projects on GitHub to run their CI services. We currently integrate with various other third-party CI services such as jenkins, bamboo, buildkite, etc, but travis would require two-way integration, which is new to us.
GitLab has integrated CI, but some people considering #movingtogitlab already have working Travis setups and no time or interest in changing code host and CI setup at the same time. Additionally, Travis CI has some features unavailable on GitLab.com, such as "just works" Mac runner support. In particular, I've been discussing this with the Quassel IRC folk: #quassel on freenode or https://github.com/quassel/quassel/blob/master/.travis.yml
We could attempt to integrate directly with Travis CI, so peoples' existing setups work whether they're on GitHub or GitLab.
There has been some discussion on their side indicating disinterest, but this was pre-github-acquisition, and they may be more willing to reconsider now that GitHub is talking about extending their vision to the full devops lifecycle. See https://github.com/travis-ci/travis-ci/issues/5931
We have an open issue about interpreting the
travis.yml files and running it in GitLab CI terms here: https://gitlab.com/gitlab-org/gitlab-ee/issues/1756
This would allow us to run many Travis pipelines directly on GitLab CI. Although the experience wouldn't be exactly the same, it might be good enough to eliminate CI as a pain point for a good proportion of people.
If we went this route, we could also consider whether to provide Mac runners on GitLab.com. We could make this a Gold feature, and open-source projects could take advantage of our free license to gain access to them. I've heard (but don't know) that Travis uses MacStadium for their machines, so perhaps we could go directly there? https://www.macstadium.com/usecases/#Build-Machines