3 ms·

While I'm glad to see competition gearing up, I don't think GitHub and GitLab are in the same ballpark yet. While I'm a big fan of their team and culture appro

While I'm glad to see competition gearing up, I don't think GitHub and GitLab are in the same ballpark yet. While I'm a big fan of their team and culture approach, we yet to see better/respected GitLab.com SLA guarantees — it still feels like they're doing too much "testing on production".

zaarn 9y ago
"testing in production" indeed. One of my repos has been stuck in limbo for over 2 months now after I attempted to migrate it to a group namespace from my own profile. Though I generally do like GitLab and favor Github alternatives over Github as I see it as a single point of failure for the FOSS community at this point.
- YorickPeterse 9y ago
  > "testing in production" indeed. One of my repos has been stuck in limbo for over 2 months now > after I attempted to migrate it to a group namespace from my own profile. Have you created an issue for this on https://gitlab.com/gitlab-com/support-forum/issues https://gitlab.com/gitlab-com/support-forum/issues?
  - zaarn 9y ago
    Yes I have, there was no response to it and it was recently closed, I believe.
    - connorshea 9y ago
      Could you link the issue so we can look into it?
      - tscs37 9y ago
        Hi, I'm not OP but I've got myself into basically the same problem; https://gitlab.com/gitlab-com/support-forum/issues/2291 https://gitlab.com/gitlab-com/support-forum/issues/2291 I tried some various solutions via CURL to get the repository unstuck (basically rewriting the URL the request is sent to since the project settings page was pointing at the wrong repo) and it basically reports an empty repo on the target (which doesn't show up for me on my profile) and a 404 on the original (which does show up on my profile)
kogepathic 9y ago
> While I'm a big fan of their team and culture approach, we yet to see better/respected GitLab.com SLA guarantees — it still feels like they're doing too much "testing on production". Agreed. However, if you need more reliability than gitlab.com it's not difficult to host GitLab yourself in a VM or on bare metal. Many companies already have their own physical servers in a DC (either colocated or leasing). Hopefully the people managing these servers know what they're doing and can give the developers a good SLA. Although some additional work on file/DB syncing would be necessary to have a hot spare.
- bayindirh 9y ago
  GitLab on hosted hardware works great. I maintain two different instances. One of them automatically updates itself, and it just works.
- rtpg 9y ago
  Or you can pay a nominal fee to GitHub and not have to manage anything... I like that Gitlab exists but I am willing to pay a lot of money to not have to manage yet another server
- jrochkind1 9y ago
  Most non-huge companies are unlikely to be able provide _more_ reliability from a self-hosted installation than a cloud hosted installation. I suspect this is true of gitlab, but if it's not, it would speak negatively to gitlab's ability to provide a reliable service. Certainly while github is occasionally down or misbehaving, there's no way any enterprise I've worked at could self-host with as much reliability as github.
edjboston 9y ago
Gitlabber here. We have a plan to address this and are kicking off our move to GCP shortly. Our top-level engineering department goal is to make gitlab.com ready for mission critical workloads and are targeting industry standard SLA's (e.g. three 9's). You can see our proposed architecture here if you're curious: https://about.gitlab.com/handbook/infrastructure/production-architecture/#infra-proposed-cloud-native https://about.gitlab.com/handbook/infrastructure/production-...

zaarn 9y ago

"testing in production" indeed. One of my repos has been stuck in limbo for over 2 months now after I attempted to migrate it to a group namespace from my own profile. Though I generally do like GitLab and favor Github alternatives over Github as I see it as a single point of failure for the FOSS community at this point.

YorickPeterse 9y ago
> "testing in production" indeed. One of my repos has been stuck in limbo for over 2 months now > after I attempted to migrate it to a group namespace from my own profile. Have you created an issue for this on https://gitlab.com/gitlab-com/support-forum/issues https://gitlab.com/gitlab-com/support-forum/issues?
- zaarn 9y ago
  Yes I have, there was no response to it and it was recently closed, I believe.
  - connorshea 9y ago
    Could you link the issue so we can look into it?
    - tscs37 9y ago
      Hi, I'm not OP but I've got myself into basically the same problem; https://gitlab.com/gitlab-com/support-forum/issues/2291 https://gitlab.com/gitlab-com/support-forum/issues/2291 I tried some various solutions via CURL to get the repository unstuck (basically rewriting the URL the request is sent to since the project settings page was pointing at the wrong repo) and it basically reports an empty repo on the target (which doesn't show up for me on my profile) and a 404 on the original (which does show up on my profile)

kogepathic 9y ago

> While I'm a big fan of their team and culture approach, we yet to see better/respected GitLab.com SLA guarantees — it still feels like they're doing too much "testing on production". Agreed. However, if you need more reliability than gitlab.com it's not difficult to host GitLab yourself in a VM or on bare metal. Many companies already have their own physical servers in a DC (either colocated or leasing). Hopefully the people managing these servers know what they're doing and can give the developers a good SLA. Although some additional work on file/DB syncing would be necessary to have a hot spare.

bayindirh 9y ago
GitLab on hosted hardware works great. I maintain two different instances. One of them automatically updates itself, and it just works.
rtpg 9y ago
Or you can pay a nominal fee to GitHub and not have to manage anything... I like that Gitlab exists but I am willing to pay a lot of money to not have to manage yet another server
jrochkind1 9y ago
Most non-huge companies are unlikely to be able provide _more_ reliability from a self-hosted installation than a cloud hosted installation. I suspect this is true of gitlab, but if it's not, it would speak negatively to gitlab's ability to provide a reliable service. Certainly while github is occasionally down or misbehaving, there's no way any enterprise I've worked at could self-host with as much reliability as github.

edjboston 9y ago

Gitlabber here. We have a plan to address this and are kicking off our move to GCP shortly. Our top-level engineering department goal is to make gitlab.com ready for mission critical workloads and are targeting industry standard SLA's (e.g. three 9's). You can see our proposed architecture here if you're curious: https://about.gitlab.com/handbook/infrastructure/production-architecture/#infra-proposed-cloud-native https://about.gitlab.com/handbook/infrastructure/production-...