Gitlab is a great service and a great alternative to github and bitbucket. But it has been quite flaky over many years and it's quite surprising they haven't prioritised system stability over everything else. https://twitter.com/gitlabstatus Gitlab has been a fully remote proponent going back a few years and these persistent reliability issues add some doubt to that model - even if there might be altogether other iss…
Gitlab.com was experiencing elevated error rates for Git, Web, and API
61–70 of 94 posts
Re: Gitlab.com was experiencing elevated error rates for Git, Web, and API
#62Re: Gitlab.com was experiencing elevated error rates for Git, Web, and API
#63We switched from self-hosted to gitlab.com a couple months back and the migration has been extremely disappointing. Pushing commits often hangs completely, and we've had a number of smaller downtimes/degradations in recent weeks that have been super disruptive. Having been Gitlab users since our inception, we're now seriously considering Github (I know - grass is always greener).
Re: Gitlab.com was experiencing elevated error rates for Git, Web, and API
#64Re: Gitlab.com was experiencing elevated error rates for Git, Web, and API
#65Re: Gitlab.com was experiencing elevated error rates for Git, Web, and API
#66/r took me a lot of effort to convince my CTO to move from Bitbucket to Gitlab. Since we have started using it ( 3 + months ), we have experienced more than 4 instances of downtime. If some one from Gitlab is reading this message, please consider a code freeze and spend some time on stabilizing the system. time to add a new backup remote to all our repos.
Re: Gitlab.com was experiencing elevated error rates for Git, Web, and API
#67/r took me a lot of effort to convince my CTO to move from Bitbucket to Gitlab. Since we have started using it ( 3 + months ), we have experienced more than 4 instances of downtime. If some one from Gitlab is reading this message, please consider a code freeze and spend some time on stabilizing the system. time to add a new backup remote to all our repos.
Re: Gitlab.com was experiencing elevated error rates for Git, Web, and API
#68/r took me a lot of effort to convince my CTO to move from Bitbucket to Gitlab. Since we have started using it ( 3 + months ), we have experienced more than 4 instances of downtime. If some one from Gitlab is reading this message, please consider a code freeze and spend some time on stabilizing the system. time to add a new backup remote to all our repos.
Re: Gitlab.com was experiencing elevated error rates for Git, Web, and API
#69I love Gitlab because I love open source and competition but Gitlab either on-prem or gitlab.com has been having growing pains ever since I started using it around 2015. And it seems to be related to scaling because it's always iffy problems like higher error rates or jobs not executing. Either way, I love our on-prem Gitlab. It's free and it hosts over 200 projects, Gitops and the whole shebang. I'm just now beginni…
Re: Gitlab.com was experiencing elevated error rates for Git, Web, and API
#70/r took me a lot of effort to convince my CTO to move from Bitbucket to Gitlab. Since we have started using it ( 3 + months ), we have experienced more than 4 instances of downtime. If some one from Gitlab is reading this message, please consider a code freeze and spend some time on stabilizing the system. time to add a new backup remote to all our repos.
We are using bitbucket atm and I can't fathom a reason to move, care to elaborate?
Australia has very weird and wide reaching laws regarding software backdoors.