3 ms·
TLDR; Why GitLab instead of GitHub? From their discussion group thread: - Good multi-platform hosted CI or at least workable integration with other (existing)
by sytelus 8y ago
TLDR; Why GitLab instead of GitHub? From their discussion group thread:
- Good multi-platform hosted CI or at least workable integration
with other (existing) CI solutions
- Hosted review tool that we don't have to maintain ourselves (though
a little bit less good than Phabricator, allegedly)
- familiar GitHub-like workflow with no requirement to install extra
software locally
- Reuse of GitHub credentials
- Realistic path forward for migrating tickets from Trac
CI is becoming Achilles heels for GitHub. Personally I would probably also add lack of fine grained permissions for contributors, inflexible diff, very basic code review tool as well.
- wodenokoto 8y agoWhat is wrong with Travis compared to GL's default CI?
- jhasse 8y agoDoes Travis have native Docker support? Last time I checked you had to manually run docker and add "sudo: true" to your .travis.yml.
- http-teapot 8y agoI am not exactly sure of your use case but we build our Docker images in Travis without problems. https://docs.travis-ci.com/user/docker/ https://docs.travis-ci.com/user/docker/
- jhasse 8y agoI want to run my build/test commands in a Docker image.
- rleigh 8y agoTravis is limited. Stuff like this https://gitlab.com/codelibre/ome-model/pipelines/37267293 https://gitlab.com/codelibre/ome-model/pipelines/37267293 is several steps beyond the capabilities of Travis. This is using platforms not supported by Travis, plus custom Docker images. And integrates with other GitLab pipelines, deploys to sonatype nexus, and stores artifacts for later use. Even if you're not using the advanced features, it's still vastly better than Travis. The Travis stock images are so out of date it's not funny.