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

91–100 of 356 posts

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

#91

Post by merb »

jobvandervoort wrote: post #80
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 stil…

Actually as already said even with the stuff mentioned here, it's really really a good project and we are happy. to [0] we've gone the CE route first since we are too small and too fast running that a EE makes sense yet (too good that you can switch between the two without any major drawbacks [http://docs.gitlab.com/ee/downgrade_ee_to_ce/README.html] and [http://docs.gitlab.com/omnibus/update/README.html#from-commu...] thats one of the major selling points, ease of use is really big in gitlab). but sitll every feature mentioned here wasn't in bitbucket so it's not like we've missing something, we've gained something while switching so we are probably whining on a really high level ;)

Oh and thanks god for the easy backup stuff, which even works while running (which other products doesn't....)

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

#92

Post by cookiesboxcar »

lima wrote: post #23

Phabricator is a great alternative, by the way. Really stable and has the best code review interface / workflow I've ever used.

I really want to love phabricator, but the local install for a new team is so painful... any thoughts about how to make that better?

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

#93

Post by cm3 »

lima wrote: post #23

Phabricator is a great alternative, by the way. Really stable and has the best code review interface / workflow I've ever used.

If only phab didn't insist on squashing a patchset into a phabricator-commit, losing the carefully created history of a branch. Cumulative mega-patches are of little use when bisecting or trying to understand how a change works by being able to follow the steps to reach the final diff. A good commit history with separate commit messages explaining the diffs goes much further in allowing someone else to understand a change than any code comment could. This is also why merge commits are useful, because they allow you to group the commits for a feature branch and not miss any of the commits involved.

Phabricator could easily include their metadata in a merge commit, instead of collapsing the branch into one mega-commit. I know some people love a flat history without merge commits, but those lose a lot of info available with a graph/tree visible when there are no forward merges.

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

#94

Post by _asummers »

jobvandervoort wrote: post #71
the_trapper wrote: post #67

Earlier quoted context omitted.

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.

You mentioned Mac runners, and if this includes iOS you'll make a killing. Figure out how to interact with a fast Android emulator and you'll be able to pull in a decent chunk of agencies that don't want to buy in house build machines.

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

#95

Post by jobvandervoort »

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…

We do our best to make CE and EE excellent, where the features that land in EE are mostly interesting for larger teams. For every feature that we don't bring to CE, this is always a hard decision.

We wrote about this here: https://about.gitlab.com/2016/01/11/being-a-good-open-source...

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

#96

Post by jobvandervoort »

merb wrote: post #91
jobvandervoort wrote: post #80

Earlier quoted context omitted.

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 stil…

Actually as already said even with the stuff mentioned here, it's really really a good project and we are happy. to [0] we've gone the CE route first since we are too small and too fast running that a EE makes sense yet (too good that you can switch between the two without any major drawbacks [ http://docs.gitlab.com/ee/downgrade_ee_to_ce/README.html ] and [ http://docs.gitlab.com/omnibus/update/README.html#from-comm…

Thanks merb!

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

#97

Post by crossman »

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.

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

#98

Post by atsaloli »

jobvandervoort wrote: post #84
atsaloli wrote: post #79

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-foun…

That's some great feedback, thanks! Any feature requests for Issues? If you plan on doing physical events, drop me an email (job at gitlab).

We've done three physical events already. :-) I'll email you! Our next physical event will be teaching at Ohio Linux Fest (https://ohiolinux.org/olfi/)

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

#99

Post by jobvandervoort »

OliverJones wrote: post #53
hochchristoph wrote: post #17

Gitlab users: How many hours per year do you spend on doing maintenance for your setup? (servers, updating, backups, troubleshooting, etc.)

Originally rigging gitlab-ce took a couple of hours, including standing up a VM, and setting up an S3 bucket for fire storage. Checking backups once a week, 3 min. Updates twice a month (using apt-get upgrade) 10 min counting integrity checks. Nuisance factor: updating gitlab-ce drops a tiny little backup file in the backups folder.

If you want to skip the mini backup before upgrades, run:

`sudo touch /etc/gitlab/skip-auto-migrations`

Docs on it here: http://docs.gitlab.com/omnibus/update/README.html

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

#100

Post by btcmike »

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.

Post reply on HN