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

71–80 of 356 posts

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

#71

Post by jobvandervoort »

the_trapper wrote: post #67
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.

My big concern when I see a company that gives away too much for free is that they are probably unprofitable and will at some point: a) Start charging for things that I'm used to having for free and/or b) Go bankrupt/get bought out by a company and disappear Do you really sell enough enterprise licenses to give all the rest of this stuff away? From a look at your site, that's the only source of profit for your compan…

Our main source of income is subscriptions that grant access to Enterprise Edition and support. That has been going very well.

We're not planning to charge for what we give away for free now. Never.

We're thinking about charging for specific Runners for our CI (such as Mac runners) and possibly for extra storage.

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

#72

Post by jobvandervoort »

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...

What do you mean with managing another tool? GitLab.com is our own instance, that we manage.

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

#73

Post by jobvandervoort »

markwillis82 wrote: post #2

We are in the middle of migrating from Bitbucket to our self hosted CE version and apart from a few permissions issues on SSH keys we have had no issues with the whole process and updating our deployment system was just a case of changing git urls. Well done Gitlab :)

Thanks Mark!

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

#74

Post by jobvandervoort »

oDot wrote: post #70

I'm working on a proper Docker setup for GitLab development which I think can be made production-ready pretty easily after the development version works. It's hard separating the different moving parts (gitlab, gitlab-workhorse, gitlab-shell+ssh, postgres/mysql, redis) but I think I will have a merge request ready soon enough :D

Wow, this sounds great! Do you have anything to share?

Do you leverage GDK? [0]

[0]: https://gitlab.com/gitlab-org/gitlab-development-kit

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

#75

Post by jobvandervoort »

krautsourced wrote: post #32

I really liked Gitlab when last I tried it, but in the end I went with https://gogs.io/ instead. For a small-ish team this felt like the most straight forward self-hosted solution. Still missing LFS though, which sucks, but it's being worked on.

We recommend Gogs for people that want to run on machines with little memory, it's great.

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

#76

Post by jobvandervoort »

OliverJones wrote: post #40
jobvandervoort wrote: post #13

Earlier quoted context omitted.

Thanks Oliver, that's great to hear. Any way we can prevent those false starts for other people?

The false starts in our conversion were mostly struggles with how to restructure our old CVS repos so they made sense in the world of git. A few of them had to do with capturing some oddball CVS specific revision and branching history. None of the false starts were due to flaws or confusion in GitLab specifically. I should, and if you pester me I will, sanitize our internal how-to documents and scripts and contribute…

Pesters!

It would be great to receive some contributions to our documentation. It has proven a big challenge to make sure it covers everything and stays up to date. We'd really appreciate it.

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

#77

Post by scrollaway »

jobvandervoort wrote: post #60
technomancy wrote: post #45

I was pretty impressed with how easy it was to get free CI runs on pushes and merge requests with my OSS game: https://gitlab.com/technomancy/bussard/commit/73e84d11ed33ff...

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.

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

#78

Post by zegerjan »

technomancy wrote: post #45

I was pretty impressed with how easy it was to get free CI runs on pushes and merge requests with my OSS game: https://gitlab.com/technomancy/bussard/commit/73e84d11ed33ff...

In case you would like to shave a couple of seconds off per build, you might want to build a docker image with both luarocks and love already installed.

This would also be a great reason to test the awesome GitLab Docker Registry[1], which is also included in CE!

[1] http://docs.gitlab.com/ce/container_registry/README.html

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

#79

Post by atsaloli »

I love how responsive our local (departmental) instance of GitLab CE is -- it's downright snappy compared to the corporate instance of JIRA. We love the issue tracking subsystem of GitLab and use it as our main ticketing system.

We've done a few talks on Git basics to help increase adoption, and are doing a free webinar "Git Foundations: Basic Concepts and Definitions" next week: https://www.eventbrite.com/e/git-foundations-basic-concepts-...

This is the sort of result it makes us very happy to achieve:

"I have got by on minimum understanding of Git for a couple of years now--this really brought up my confidence in using Git. After I learned the Git internals, the esoteric commands really started falling into place." --Nicholas Santucci, Monitoring and Performance Engineer

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

#80

Post by jobvandervoort »

merb wrote: post #65

We moved from BitBucket on premise to GitLab CE on premise. Actually most things now just works. Updating is a breeze. Instead of downloading a installer and copying / fixing server.xml we can just do a apt update && apt upgrade -y. Some things are a little bit akward but BitBucket didn't had this, too: - FF only merges is only EE (too bad that would be a really major selling point even for CE, squash button would be…

Thank you for the awesome detailed feedback. Responded point by point below:

> FF only merges is only EE (too bad that would be a really major selling point even for CE, squash button would be unnecessary)

These are always hard choices to make for us. We wrote about these decisions here [0].

> CI is a little limited compared to a full blown Jenkins - We hit a CI bug which still shows up "Running" Pipelines

We're still young, but confident that we'll get there! CI/CD is a major focus for us and we're working really hard to improve it with every release. Love to get specific feature requests for things that we miss in comparison with Jenkins.

Regarding the bug: I've pinged our PM on it.

> Artifacts API is limited to everything or nothing

Could you elaborate? I know we have numerous improvements planned, but I'm not sure about their prioritization.

> CI Stages can be defined as trigger only but you can't have multiple triggers that starting different things (considering a production trigger and a testing trigger while you don't want the 'manual' thing directly in GitLab, especially when integrating into other systems makes this a flaw)

Hm, could you write a feature proposal for this [1]? It sounds like a great improvement.

> No Custom CSS (yeah our logo isn't 72px x 72px...)

We're extremely hesitant to do this, as we make many changes between releases. This would break custom css with every upgrade, in turn resulting in a worse experience.

I rather hear suggestions about specific parts in the interface that should be made customizable or suggestions about changes to the UI altogether.

Although I'm not a fan of custom css, there is an issue to discuss this and I welcome your input there [2].

[0]: https://about.gitlab.com/2016/01/11/being-a-good-open-source...

[1]: https://gitlab.com/gitlab-org/gitlab-ce/issues/new

[2]: https://gitlab.com/gitlab-org/gitlab-ce/issues/15635

Post reply on HN