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

GitLab 8.15 Released

about.gitlab.com

Post reply on HN
Print view View original

41–50 of 117 posts

Re: GitLab 8.15 Released

#41

Post by gtaylor »

meddlepal wrote: post #26
connorshea wrote: post #18

Earlier quoted context omitted.

Thanks for the honest feedback, it's genuinely useful for improving the product. Out of curiosity, why use the Docker image over our Omnibus package? Omnibus is generally what we recommend, but if that's not good enough we'd love to know how it can be improved.

Is there a Omnibus package for Kubernetes (perhaps a Helm package?) I'd be very interested in that. FWIW: I ran GitLab at my previous company (2yrs agoish) because GitHub was a non-starter for political reasons. We loved it! Keep rocking.

There is indeed a helm package, gitlab-ce.

Re: GitLab 8.15 Released

#42

Post by thanksgiving »

cbdfghh wrote: post #35
sergiotapia wrote: post #21

I'm curious how you guys build features for EE. Is it a completely separate Rails project you handle manually to keep base features in sync with the community edition? EE is open source but requires a license. Do you just trust companies won't download the source code and run it. Do you have heartbeat code injected somewhere to ping servers that are running EE to homebase? I'm thinking of starting a project, charge m…

>EE is open source It is _not_. You cannot distribute it. That makes it not open source.

yeah, the term I'd use is source available? anyway, I agree with the idea that "open source" is a dirty term, an attempt to subvert the free software movement. But that is a battle for another day.

Someone else put it better than I could:

> Likewise a Source Available is not necessarily Open Source, but Open Source is necessarily Source Available.

https://haacked.com/archive/2006/07/26/CodeAvailableVsOpenSo... (requires you to accept github cert because https is difficult for some reason)

Blog github at https://github.com/Haacked/haacked.com

Re: GitLab 8.15 Released

#43

Post by spinningarrow »

connorshea wrote: post #18
contingencies wrote: post #17

@Gitlab: The features are great but the interface setup is shocking. That whole video assumes you have a K-cluster going already, and is a maze of this-thing, that-thing, auth-thing, copy-thing, etc. Have you guys ever tried interviewing users who are new or maintaining a Gitlab instance over major version upgrades? It's painful. The 'quick fix' for setup these days is supposed to be to use a docker image... but the…

Thanks for the honest feedback, it's genuinely useful for improving the product. Out of curiosity, why use the Docker image over our Omnibus package? Omnibus is generally what we recommend, but if that's not good enough we'd love to know how it can be improved.

I haven't tried omnibus but I'd vote for docker too after being spoilt by setting up and maintaining a Discourse instance. They've done an absolutely fantastic job in making installation and updates painless.

Re: GitLab 8.15 Released

#44

Post by CapnCrunchie »

softinio wrote: post #30

I recently registered to try gitlab. I received unprecedented large amounts of spam from them daily with no unsubscribe button. I finally emailed them to stop the spam and they did but not completely I received more but had unsubscribe this time. Unsubscribed so lets see what happens. One more spam and I will close my account and never try them again GitHub is great, does the job incredibly well, doesn't get in the w…

Hey, I do marketing at GitLab, and this is definitely not something that should be happening. If you want to email me at mitchell [at] gitlab [.] com with the email that you signed up to our service with I'd love to look into why you were sent so many emails.

Re: GitLab 8.15 Released

#45

Post by sdesol »

angry-hacker wrote: post #39

Are there notable projects or organizations moved to gitlab.com? On top of my head I only know f-droid that is there. I use it for personal use and love it, would love if more projects moved away from github.com, especially open source.

I talked about GitLab and how they can compete against GitHub in this past comment

https://news.ycombinator.com/item?id=11155293

and at the present moment, they are still pretty far from being able to convince notable projects to leave github.com for gitlab.com The biggest issue right now, is there is a measurable difference between gitlab.com and github.com, which is, it's much slower.

GitLab is working on this and I have no doubt this will become a non-issue in the future, but they still have to deal with the fact that you can't compete with being "as good as". Even if gitlab.com becomes as good as github.com, they will still have a difficult time, to convince others to leave github.com for gitlab.com

I guess my point is, since github.com is the incumbent, the only way that gitlab.com can become the next place to collaborate, is they have to make it clear, that they are better than github.com They can't strive for equality, since you can't compete with "as good as".

Re: GitLab 8.15 Released

#46

Post by connorshea »

angry-hacker wrote: post #39

Are there notable projects or organizations moved to gitlab.com? On top of my head I only know f-droid that is there. I use it for personal use and love it, would love if more projects moved away from github.com, especially open source.

Danger hosts their website with GitLab Pages[0], iTerm hosts their issue tracker there[1], the game Xonotic is hosted on GitLab.com[2], and then VLC[3] and GNU[4] both have their own instances of GitLab.

[0]: https://gitlab.com/danger-systems/danger.systems

[1]: https://gitlab.com/gnachman/iterm2/issues

[2]: https://gitlab.com/groups/xonotic

[3]: https://code.videolan.org/videolan/VLCKit

[4]: https://git.gnu.io/explore/projects

Re: GitLab 8.15 Released

#47

Post by maktouch »

I love gitlab! We just deployed our review app deployment to Kubernetes (create a new subdomain in route53, create a new namespace in k8s, create all kubernetes manifests in that namespace, create ingress manifest, boom!).

Here's some thing I wish for gitlab:

1. On merge, run "stop_review" so that we don't end up with a lot of old review apps.

2. I wish you could take over https://github.com/sameersbn/docker-gitlab or offer something similar. I find it a little crazy that you have a single docker image for redis, gitlab, postgresql. There's multiple reason why we don't want to use this, but the simplest is: we already have mysql running (and feel no need to move to pgsql), and we already have experience in running redis.. I kinda like my containers to do 1 thing and 1 thing well.

Merry Christmas, thanks for this patch!

Re: GitLab 8.15 Released

#48

Post by lbotos »

napsterbr wrote: post #34
connorshea wrote: post #28

Earlier quoted context omitted.

We've spent quite a bit of time this year improving performance, GitLab.com is still slower than it should be but it's a lot better now than it was in January. Self-hosted instances that meet the recommended specs are already fairly performant, though we're always working to improve things regardless. As mentioned in the blog post, this release we decreased page size a lot (from 1800kb to 718kb for a given Merge Requ…

Don't know exactly why you decided against moving to bare metal, but IMO you definitely should. We've got tremendous improvements moving to metal. I also can't recommend OVH enough. Best price on market plus great hardware and uptime. Technical support isn't the best but you shouldn't need it anyway.

I also work at GitLab on a non-infra team. Here is Sid's explanation:

https://gitlab.com/gitlab-com/infrastructure/issues/727#note...

I, personally, was apprehensive of going to bare metal for most of the reasons that Sid lists in the above message, and I think that making the app just _better_ is where we should focus before we try and run to pure hardware to solve the problem.

Re: GitLab 8.15 Released

#49

Post by storrgie »

connorshea wrote: post #18
contingencies wrote: post #17

@Gitlab: The features are great but the interface setup is shocking. That whole video assumes you have a K-cluster going already, and is a maze of this-thing, that-thing, auth-thing, copy-thing, etc. Have you guys ever tried interviewing users who are new or maintaining a Gitlab instance over major version upgrades? It's painful. The 'quick fix' for setup these days is supposed to be to use a docker image... but the…

Thanks for the honest feedback, it's genuinely useful for improving the product. Out of curiosity, why use the Docker image over our Omnibus package? Omnibus is generally what we recommend, but if that's not good enough we'd love to know how it can be improved.

Omnibus makes a ton of assumptions about how many things you want bundled, as well as the monolithic configuration is daunting. I'd suggest breaking up into smaller containers for each service. No matter what container medium you choose, the philosophy of omnibus isn't something you want to 'containerize' as it is.

Re: GitLab 8.15 Released

#50

Post by theptip »

gtaylor wrote: post #41
meddlepal wrote: post #26

Earlier quoted context omitted.

Is there a Omnibus package for Kubernetes (perhaps a Helm package?) I'd be very interested in that. FWIW: I ran GitLab at my previous company (2yrs agoish) because GitHub was a non-starter for political reasons. We loved it! Keep rocking.

There is indeed a helm package, gitlab-ce.

Aha! I was looking for this recently. Doesn't appear to be on https://about.gitlab.com/installation/, which is where I stopped my search for it.
Post reply on HN