3 ms·

Let us know what projects you miss seeing integrated with GitLab and we'll try our best to convince them, help them in any way to make sure it happens! As othe

Let us know what projects you miss seeing integrated with GitLab and we'll try our best to convince them, help them in any way to make sure it happens! As other point out, you should be able to use GitLab CI instead of Travis, they configure very similarly. That said, I'd welcome them integrating fully with us as well.

ohstopitu 10y ago
I've used Gitlab CI before and I do like it, but TravisCI allowed for some granular control that Gitlab CI does not have (or that I am doing wrong) - for example, ability to run specific tests in case of pull/merge requests (TrasisCI has an environment variable for it). As for other projects - the most important one for me was clubhouse.io (Gitlab Issues is great but just not as good as clubhouse.io)
- jobvandervoort 10y ago
  > I've used Gitlab CI before and I do like it, but TravisCI allowed for some granular control that Gitlab CI does not have (or that I am doing wrong) - for example, ability to run specific tests in case of pull/merge requests (TrasisCI has an environment variable for it). Ah interesting! You can't do this now with GitLab, but we're working on supporting merge requests as special cases [0]. > As for other projects - the most important one for me was clubhouse.io (Gitlab Issues is great but just not as good as clubhouse.io) Clubhouse sure looks nice! GitLab Issues is getting better every release and in 9.0 (March 22nd), we have some big changes for Issue Boards. I've asked our PM on Issues (Victor) to check out Clubhouse and hopefully we can convince them to integrate with us in some way. [0]: https://gitlab.com/gitlab-org/gitlab-ce/issues/23902 https://gitlab.com/gitlab-org/gitlab-ce/issues/23902
lloeki 10y ago
GitLab CI and gitlab-multi-runner is nice and all (really!) but Travis CI provides (free) OS X runners, which is mandatory for some projects.

ohstopitu 10y ago

I've used Gitlab CI before and I do like it, but TravisCI allowed for some granular control that Gitlab CI does not have (or that I am doing wrong) - for example, ability to run specific tests in case of pull/merge requests (TrasisCI has an environment variable for it). As for other projects - the most important one for me was clubhouse.io (Gitlab Issues is great but just not as good as clubhouse.io)

jobvandervoort 10y ago
> I've used Gitlab CI before and I do like it, but TravisCI allowed for some granular control that Gitlab CI does not have (or that I am doing wrong) - for example, ability to run specific tests in case of pull/merge requests (TrasisCI has an environment variable for it). Ah interesting! You can't do this now with GitLab, but we're working on supporting merge requests as special cases [0]. > As for other projects - the most important one for me was clubhouse.io (Gitlab Issues is great but just not as good as clubhouse.io) Clubhouse sure looks nice! GitLab Issues is getting better every release and in 9.0 (March 22nd), we have some big changes for Issue Boards. I've asked our PM on Issues (Victor) to check out Clubhouse and hopefully we can convince them to integrate with us in some way. [0]: https://gitlab.com/gitlab-org/gitlab-ce/issues/23902 https://gitlab.com/gitlab-org/gitlab-ce/issues/23902

lloeki 10y ago

GitLab CI and gitlab-multi-runner is nice and all (really!) but Travis CI provides (free) OS X runners, which is mandatory for some projects.