The integrated CI is a big win.

Everything else requires maintaining more pieces of infrastructure and is not integrated so nicely.

I agree that Gitlab is far from perfect, but it's the best solution in this space IMO.

I think there are some areas where GitLab can improve their CI story, but I agree that having a One Stop Shop for that is actually very compelling.

This month we're coming out with scheduled CI builds and next month with multi-project builds. What improvement would you like to see in our CI?

* compatibility with msys2. It's one of the best environments on Windows for building cross-platform apps (where cross-platform is Windows, OSX, and Linux). Ideally, I'd like to run a Windows VM for the CI build and have artifact uploads, all through the msys2 shell. I see a single rumbling here: https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/issues/...

Great idea, I've marked it Accepting Merge Requests https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/issues/...

> What improvement would you like to see in our CI?

The ability to view build reports, such as test results and the like.

Tracked many times, in various forms: https://gitlab.com/gitlab-org/gitlab-ce/issues/13227 (73 votes), https://gitlab.com/gitlab-org/gitlab-ce/issues/18664 (67 votes), https://gitlab.com/gitlab-org/gitlab-ce/issues/10982 (53 votes), https://gitlab.com/gitlab-org/gitlab-ce/issues/17081 (22 votes), https://gitlab.com/gitlab-org/gitlab-ce/issues/23618 (a mere 5 votes).

Thank you for sharing your thoughts: you're totally right, this feature has much interest by the community and is an high priority. By the way, this is also a very complex topic, as you need to provide great flexibility but at the same time the best UX. As usual, we move by iterating on the issue by little steps: first of all we need the basic building blocks, on top of them we can create the final feature. I mostly agree that test results and other "custom" information must be extracted automatically from logs, but we need to provide a generic model that can be easily adapted to everyone. Iterations on that brought us code coverage information, artifacts for failed jobs and browsing and online display of artifacts (ready to be released in 9.2), and we provide also workarounds, like using GitLab Pages, that can solve some scenario until the work is completed. I'd like also to mention our current effort in supporting CodeClimate (https://gitlab.com/gitlab-org/gitlab-ce/issues/4044). We will continue on this path (one of the issues you mentioned has the "direction" label), always open in receiving feedback and promoting collaboration at any level.

Or that prefer open source tools.

There are more open source Source Code management tools, such as RhodeCode, or Gitea

Yes, but that does not diminish my potential explanation for why people sometimes do not wish to use github but gitlab instead, which is the subject of the thread (see title).

Try Gogs. It's less feature rich but it works very well and is an absolute breeze to deploy.

I absolutely second that. I moved from gitlab to gogs being tired of the gitlab setup mess, and it works so well. On the ci side I use drone and both products integrate perfectly

I really fanatically loathe Rube Goldberg machine software. "Once you've installed Postgres, MySQL, MongoDB, and Redis, make sure your Ruby version is newer than 2.0 and your NodeJS version is newer than..."

Have you checked out gitea, the community-developed fork of gogs?