Live data from Hacker News

Gitlab 11.8 Released

about.gitlab.com

11–20 of 57 posts

Re: Gitlab 11.8 Released

#11
post #2

Gitlab is great and I have used it for years but I recently switched to Gogs for self hosted repositories because it is much faster, easier to set up and walk in a park to maintain. It doesn't have all the features (bloat) that Gitlab has but it can probably satisfy >95% of git users.

Hello! Since GitLab is a single application that covers the entire software development lifecycle, we're a bit "bigger" than Gogs, which only tackles SCM. We have a plan to make GitLab use less resources, including forming a team to specialize in this area, and we're really grateful for your feedback. :)

> We have a plan to make GitLab use less resources

I used to use gitlab at work daily and releases would mention how performance is being tackled consistently. However, I have not seen any large improvements at all, suggesting that there is an impenetrable wall made of the underlying technologies.

Gitlab is based primarily on Ruby-on-Rails, which doesn't particularly shine with neither memory usage nor performance. What sort of effort would even reduce the use of resources significantly, short of a rewrite?

Re: Gitlab 11.8 Released

#12
I really like the update pace of Gitlab. Our teams are all based on an on-prem EE (low tier) and it's been a pleasure to receive a steady stream of valuable updates.

Passing on all the good things that Gitlab does for us already; I _really_ wish gitlab would push to make more of the Project Management features accessible to the lower tiers (maybe even CE). Epics and Roadmaps linked to Gitlab's SCM and DevOps features would be a _real_ contender to JIRA/Confluence in the market but it's currently hidden behind a very steep ~100$/m "ultimate" plan.

Re: Gitlab 11.8 Released

#13

You know, there was a thread the other day about a new release announcement for some IDE. It was quickly removed, on grounds that the Hacker News FAQ says you shouldn't repost something " If a story has had significant attention in the last year or so ". I remember thinking that it was a real stretch to interpret different release announcements, separated by months, as "duplicate" posts. But this was coming from dang…

I’ve submitted it a few times, just because I use it and like it, interested in discussion about it. I don’t know if I agree with the rule (a whole year?), but I’ll stop submitting it.

Re: Gitlab 11.8 Released

#14
post #11

Earlier quoted context omitted.

Hello! Since GitLab is a single application that covers the entire software development lifecycle, we're a bit "bigger" than Gogs, which only tackles SCM. We have a plan to make GitLab use less resources, including forming a team to specialize in this area, and we're really grateful for your feedback. :)

> We have a plan to make GitLab use less resources I used to use gitlab at work daily and releases would mention how performance is being tackled consistently. However, I have not seen any large improvements at all, suggesting that there is an impenetrable wall made of the underlying technologies. Gitlab is based primarily on Ruby-on-Rails, which doesn't particularly shine with neither memory usage nor performance. W…

This "rails/ruby is slow" myth really needs to die. Sure, rails is too slow for certain very large companies at very large scales, and if you're in this position you already know it. However, rails is fast enough for 99.5% of usecases, gitlab included.

As to memory usage, I will concede it is often somewhat high with rails, but there are solutions, such as jemalloc that have helped me in the past.

Re: Gitlab 11.8 Released

#15
Congrats on the new release!

Since GitLab for Education was announced I've been trying to get our college signed up for it, but it's been difficult so I was hoping I might be able to share some GitLab for Education Requests:

Working in a community college it's been really tricky to get the agreement signed for us to take advantage of this at all (that's more of an issue with the way we work in particular, but I just wanted to throw it out there that it would be nice if we could sign up for the licenses completely online without needing to wait and get an agreement signed because for example our president doesn't want to do an esignature so that means sending it over to their office for signature, waiting a long while, getting it back, and then finding out our deadline passed and haven't to try it all over again so if that process could be changed, or better yet removed, that would be great).

Related to the GitLab for Education license limitations...I originally though the Education licensing would cover usage for our IT Department staff as well, but it definitely seems to be limited to just Faculty/Staff type usage which ends up being a bummer for us since now I can't promote it anymore internally with us a free option we can sign up for anymore and other ideas I was potentially thinking of (the Group Issue Boards seemed like it could potentially be a nice way to organize Kanban Boards across the college and make it so that staff from other areas outside of IT could make use of Kanban Boards too...we've been using Kanboard inside of IT for a few years now, but haven't made a strong push to have other departments use it). In terms of affordability, that would limit us to licensing GitLab primarily for IT stuff only + for 10 users that's already going to be a pretty big cost for our small college / IT department.

Lastly, I know there's Wiki functionality and GitLab Pages already and that can be used for documentation to a degree, but is there any work towards building/including some sort of Confluence alternative into GitLab as well?

Right now we'd like start using some sort of nice, comprehensive documentation option, but I'm not really sold on Confluence at the moment. Admittedly, right now with the info about us needing to license GitLab for our IT department staff as well being fairly new to me that's thrown the whole idea of using GitLab out the window (almost), but the lack of a Confluence option built-in to GitLab would be another potential blocker for us (I do like the idea of having everything all under one system if possible to simplify usage for us).

tldr: If you can make edu licensing completely free (for staff too) and simple to use/signup for (without an agreement needing to be signed), plus add a Confluence alternative that would be awesome!

Re: Gitlab 11.8 Released

#16
post #5

Earlier quoted context omitted.

Did you look at Gitea before you stood up Gogs? I'm looking at both and will choose one shortly, any insight is most appreciated.

Gitea has more options and features, but it is more bleeding edge. Unkwon (Gogs author) handles contributions to Gogs very carefully, taking painstakingly attention to the code being submitted. That has resulted on a very stable, and reliable software. You decide. :-)

To rephrase what you said, Gitea is more community driven. You'd have a better chance contributing and fixing issues that impact you with Gitea, compared to Gogs.

Personally I switched over to Gitea.

One of the more tangible differences between the two is that Gitea bundles all the web assets into the executable used to run the service, so you just have a single exe replace on upgrades. It's been a while since I've used Gogs, but looking at their latest info you still need to remove some folders and not others when updating Gogs, because some of them are template and static files used by the web server.

Re: Gitlab 11.8 Released

#17
post #2

Gitlab is great and I have used it for years but I recently switched to Gogs for self hosted repositories because it is much faster, easier to set up and walk in a park to maintain. It doesn't have all the features (bloat) that Gitlab has but it can probably satisfy >95% of git users.

Yes but Gogs is self-hosted whereas Gitlab offers hosting solutions.

Here's a link to the self-hosted GitLab https://about.gitlab.com/pricing/#self-managed

Re: Gitlab 11.8 Released

#18

You know, there was a thread the other day about a new release announcement for some IDE. It was quickly removed, on grounds that the Hacker News FAQ says you shouldn't repost something " If a story has had significant attention in the last year or so ". I remember thinking that it was a real stretch to interpret different release announcements, separated by months, as "duplicate" posts. But this was coming from dang…

(Note: obviously my opinion, not the actual rules)

I do think the rule should be based on the content of the release rather than the timing. If the software contains major new features every month that could be relevant to the HN audience I see no reason to remove the post, it's _new_ information being posted on Hacker _News_. (I haven't seen the referenced IDE update post so I don't have an opinion on it either way.)

Re: Gitlab 11.8 Released

#19

You know, there was a thread the other day about a new release announcement for some IDE. It was quickly removed, on grounds that the Hacker News FAQ says you shouldn't repost something " If a story has had significant attention in the last year or so ". I remember thinking that it was a real stretch to interpret different release announcements, separated by months, as "duplicate" posts. But this was coming from dang…

I’ve submitted it a few times, just because I use it and like it, interested in discussion about it. I don’t know if I agree with the rule (a whole year?), but I’ll stop submitting it.

Oh, to be clear... I'm perfectly HAPPY with release announcements, and believe that strict interpretation was ridiculous.

I was simply taking issue with the inconsistency, arbitrary interpretation, selective enforcement, etc.

Re: Gitlab 11.8 Released

#20
post #14
post #11

Earlier quoted context omitted.

> We have a plan to make GitLab use less resources I used to use gitlab at work daily and releases would mention how performance is being tackled consistently. However, I have not seen any large improvements at all, suggesting that there is an impenetrable wall made of the underlying technologies. Gitlab is based primarily on Ruby-on-Rails, which doesn't particularly shine with neither memory usage nor performance. W…

This "rails/ruby is slow" myth really needs to die. Sure, rails is too slow for certain very large companies at very large scales, and if you're in this position you already know it. However, rails is fast enough for 99.5% of usecases, gitlab included. As to memory usage, I will concede it is often somewhat high with rails, but there are solutions, such as jemalloc that have helped me in the past.

Gitlab most certainly not included! Its perf is awful in comparison to any modern stack (including some php ones unfortunately).
Post reply on HN