Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Moving to GitLab: Yes, it's worth it

about.gitlab.com

Post reply on HN
Print view View original

101–110 of 356 posts

Re: Moving to GitLab: Yes, it's worth it

#101

Post by jobvandervoort »

microcolonel wrote: post #33
jobvandervoort wrote: post #4

As always, we're happy to answer any questions about GitLab.

I feel as though some of the recent UI changes were cosmetic and degraded the experience. I was especially unhappy about the sidebar being pushed into a hamburger menu (which can be pinned open, mind you). I'd really like for UI updates in the future not to be jarring and seemingly pointless. I really liked the UI right before the overhaul, only minor tweaks seemed truly necessary. Many of the tweaks I would have sug…

I've asked some people that work on our UI to respond, but we're aware that we have some ways to go before it's really good and that the large changes that we're making can be painful at first.

> Other than that; I'd like to say that I have really liked using Pivotal Tracker for developing software. It has a rigid pipeline between requirements and results. Configurability ruins some productivity tools. It would be swell to have something like "Pivotal Tracker lite" associated with GitLab (in that GitLab CI is). It's not a difficult kind of software to do reasonably well, and it would make GitLab the ultimate software project productivity suite.

Could you elaborate on what kind of features we'd be required to add given your suggestion? What do we miss?

Re: Moving to GitLab: Yes, it's worth it

#102

Post by d0100 »

chrishacken wrote: post #41
jobvandervoort wrote: post #31

Earlier quoted context omitted.

I'll leave the marketing talk to less biased people here, but do note that: - you can use GitLab.com for free: unlimited public and private repositories, unlimited collaborators, free hosting of your Docker images, free hosting of your static site with any static site generator and free CI / CD - GitLab CE is fully open source (MIT Expat). You can easily install it anywhere you want.

"you can use GitLab.com for free" It seems like that is the main selling point. However, I think that most of us don't want the extra weight of managing yet another tool. Thus why many of us use GitHub to begin with and not something else...

Isn't GitLab.com managed? It's a bit slow when using the web interface, but it's free.

Re: Moving to GitLab: Yes, it's worth it

#103

Post by redwood »

thinkMOAR wrote: post #86

I would like to see that there is just one gitlab version, and that the enterprise features are simply available in the community edition too. I will not pay just for a feature like repo mirroring, but it's i think a feature many people will use and or utilise when moving, migrating to a gitlab setup. But it is the one and only feature i am missing so not worth upgrading to EE for me. As soon as an alternative (open…

If you think about what you're asking: youre asking for folks who build infrastructure you rely on to have no viable way of creating a self sustaining business model. Aka no virtuous circle. No development. This perspective is a classic tragedy of the commons situation and makes perfect sense for you to have as an individual. But it's sad.

Re: Moving to GitLab: Yes, it's worth it

#104

Post by [deleted] »

jobvandervoort wrote: post #87
Svenskunganka wrote: post #34

Earlier quoted context omitted.

Was over a year since I last used GitLab, and I wonder if the resource usage and response times of a self-hosted instance has improved? Back then we were 3 developers having roughly 20 repos. The memory usage was over 2GB when idle and response times were at best between 2-3 seconds. Testing your hosted version, loading this page[1] for example takes 4 seconds (3.6s TTFB). Don't get me wrong, the platform and its fea…

If you run your own instance of GitLab now, it will be fast. Since last year March we've grown from 9 to now 100 people, many of which dedicated to performance. GitLab.com is slow, occasionally painfully so. We're very aware of that and are working to improve that. You're welcome to watch or contribute here [0]. [0]: https://gitlab.com/gitlab-com/infrastructure/issues/59

[deleted]

Re: Moving to GitLab: Yes, it's worth it

#105

Post by jobvandervoort »

btcmike wrote: post #100
crossman wrote: post #97

FWIW, I recently transferred my side project from bitbucket to gitlab and I'm really happy with it. The issue tracker is significantly better, and the built in CI seems great but I haven't started using it yet since I already have codeship going.

I did the same last month and then transferred back to bitbucket. The response time on gitlab.com was painfully slow. That extra 2-3 seconds waits for each commit was enough to drive me back. I still use github for professional projects and bitbucket for personal ones.

I can imagine that GitLab.com was too slow. We just (two days ago) added another storage, where new repositories are created. That should be faster.

I hope you're willing to give GitLab another try when we've improved the performance of GitLab.com or by hosting it yourself.

Follow our work on GitLab.com performance here: https://gitlab.com/gitlab-com/infrastructure/issues/59

Re: Moving to GitLab: Yes, it's worth it

#106

Post by cm3 »

igtztorrero wrote: post #82

If your concern is cost, bitbucket always have free private repositories. If your looking for privacy and protect your sacred code, install gitlab on one of your server or vps. Thats what we do at SAIT

Fair point, but it's important not to fool ourselves in terms of data safety or at least specify what we mean when we say "it's private on your vps".

If your code is private and not meant to fall into external hands, then putting it on a VPS won't protect it. The only way is to put it on a machine that's only used from workstations that access it in a local-only fashion, inside containers/vms that have no way to contact the outside world. This means the build process may not access the internet and has to rely on a cache of external libs if needed and allowed. This also implies that network config won't allow access as forbidden via VLANs or similar measures.

If someone wants to steal your code, grabbing it from your vps won't be harder than doing the same on github/gitlab because the procedures to get access will be very similar.

I suspect by private code you mean code which shouldn't be publicly clone'able but isn't behind locked doors otherwise.

Re: Moving to GitLab: Yes, it's worth it

#107

Post by bovermyer »

btcmike wrote: post #100
crossman wrote: post #97

FWIW, I recently transferred my side project from bitbucket to gitlab and I'm really happy with it. The issue tracker is significantly better, and the built in CI seems great but I haven't started using it yet since I already have codeship going.

I did the same last month and then transferred back to bitbucket. The response time on gitlab.com was painfully slow. That extra 2-3 seconds waits for each commit was enough to drive me back. I still use github for professional projects and bitbucket for personal ones.

I had the same experience. The other thing I would add is that the social side of Gitlab is not as refined as GitHub's. There's no "timeline," for example.

I pay for GitHub and enjoy it.

Re: Moving to GitLab: Yes, it's worth it

#109

Post by jobvandervoort »

scrollaway wrote: post #77
jobvandervoort wrote: post #60

Earlier quoted context omitted.

We're working hard on making CI super easy to use and setup. If you want to give it a spin, check out our recent blog post on starting from 0: https://about.gitlab.com/2016/07/29/the-basics-of-gitlab-ci/

I was trying to look into Gitlab Runner the other day. How decoupled is it from Gitlab itself? Would I be able to somewhat easily write a completely different UI, with a different framework/language (say, Django), hook it all up to Github/Gogs and use Gitlab runner for the jobs themselves? Because if that's what it is, that is pretty kickass.

AFAIK you would not be able to do that. I've asked the author of Runner to comment here.
Post reply on HN