Hacker News Reader

Comment by ohstopitu | Hacker News Reader

I love Gitlab but sadly, quite a lot of services that offer free accounts for open source projects (TravisCI comes to mind), generally don't integrate with Gitlab

It's one of the few reasons why I am still using Github :( .

View on HN

I'm in a similar situation. I have a Gitlab account and am fine using it for personal projects but it's challenging to convince existing projects to move their repositories over. I'll start considering gitlab.com more seriously after the performance improvements mentioned in another thread here are rolled out.

I would prefer if Gitlab CI was a separate product but there probably isn't a lot of benefit for Gitlab to do that. If you want to have Gitlab CI job results displayed in your Github branches you could try this test service:

https://github.com/avtar/docker-push-ref-gitlab

> I love Gitlab but sadly, quite a lot of services that offer free accounts for open source projects (TravisCI comes to mind)

Isn't there a "but sadly I don't love its CI" missing from the middle of this? Why is Travis the problem?

Gitlab has its own CI. Are you sure you need Travis? Especially if you're the owner of project and can make a switch. Imo all open source programs should make the switch. Gitlab stands better for the community that github does.

I've yet to find something I needed that wasn't supported - or that there wasn't a better option available that did support it.

TravisCI for instance, is easily replaced in all of my projects with Gitlab's integrated CI.

I feel this way too. Not specifically about travis but about providing github integration as the only option Git is supposed to be distributed! How hard is it to ask people to provide a git url and tell them to push events to a webhook?

Generally I have the opinion that the CI of gitlab is much more powerful because of real Docker usage (and also works on private repos for free). Speaking about the gitlab CI... why is there no status or statistics page about it on status.gitlab.com and why is a new build pending over 30 minutes currently (now) ?

You can find some public monitoring regarding CI on GitLab.com here [0].

I agree that we should have some status on CI as well, made an issue [1].

[0]: http://monitor.gitlab.net/dashboard/db/ci

[1]: https://gitlab.com/gitlab-com/infrastructure/issues/1360

Wow that gitlab monitor on [0] looks really great. Thanks! Can I ask which software that is? :)

It's Grafana [0], backed by Prometheus [1].

[0]: https://grafana.com/

[1]: https://prometheus.io/

Travis has supported Docker Container based builds for quite a while now.

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.

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)

> 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

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.

Reply on news.ycombinator.com