Live data from Hacker News

Gitlab 10.7 Released

about.gitlab.com

11–20 of 84 posts

Re: Gitlab 10.7 Released

#11

I implemented the HTTPS-only Pages feature in this release. I just wanted to say that GitLab is a great project to contribute to, with a very friendly and professional community! Definitely recommend to anybody interested in contributing to a project themselves. [1] https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/16273 [2] https://about.gitlab.com/contributing/

Thank you.

The issue thread/request for this had been open for something like 2 years and I waited patiently for someone braver than me to implement it.

Now my custom domain on GitLab Pages automatically redirects to HTTPS. I'm happy.

Next up is to add an option to automatically renew Let's Encrypt certs for GitLab Pages.

Re: Gitlab 10.7 Released

#12
post #7
post #2

I know its not as sexy as new features, but I really wish gitlab took a look at performance. Currently its sitting at 9GiB of Memory on my dedicated server box for basically no users. I tried it on smaller instances but it was so painfully slow I ended up getting a cheap dedicated server from Hetzner.

They have a dedicated section about performance improvements in the release notes. It links to a list of 53 commits from this release targeting performance: https://gitlab.com/groups/gitlab-org/-/merge_requests?scope=...

Thanks Scott for linking to that. We're very much trying to improve the performance of GitLab.

I do think that most of our performance improvements are to improve the end-user experience. So I totally understand dijit's request to reduce memory. Today we recommend 4GB of memory to run GitLab https://docs.gitlab.com/ee/install/requirements.html#memory

One big thing would be if we can run the Ruby code multithreaded https://gitlab.com/gitlab-org/gitlab-ce/issues/3592 You can see I created that issue 2 years ago and there has been recent activity on it.

Right now GitLab the company is focussed on making complete DevOps https://about.gitlab.com/2017/10/11/from-dev-to-devops/ happening. So any help on the multi-threading is appreciated. The first thing would be to implement https://github.com/covermymeds/rubocop-thread_safety

Re: Gitlab 10.7 Released

#13
Rather comically, I've been unable to import my Gitlab.com repo into an on-prem Gitlab EE instance for the last 3-4 months, due to an import bug -- seems like that's the one import that should be easy to test thoroughly, but apparently not.

Here's to hoping that this version happens to have fixed the issue!

Re: Gitlab 10.7 Released

#14
post #2

I know its not as sexy as new features, but I really wish gitlab took a look at performance. Currently its sitting at 9GiB of Memory on my dedicated server box for basically no users. I tried it on smaller instances but it was so painfully slow I ended up getting a cheap dedicated server from Hetzner.

It might be worth mentioning that they use jemalloc which greedily allocates memory. I "found out" while running into an issue and disabled it[1] which shaved a fair amount of memory from allocation. At the end of the day I guess it didn't matter - for me - seeing how I didn't need that memory for anything else.

Also, the cookbook for setting up postgres also takes your total ram into account.

1: https://gitlab.com/gitlab-org/omnibus-gitlab/issues/3313

Re: Gitlab 10.7 Released

#15
I wish I could understand the value add of yet another IDE. The whole reason for tech to exist is to improve things around the world, and yet brilliant minds are still spending years building one IDE after another.

"Switching branch and remembering branch names..." is a simple git status. On vim, you can get a file browser on the left by using nerdtree plugin, and to write commit messages on the right side you simply just have another tmux window open for git or other unix commands. Building a new IDE is solving a very marginal problem that could potentially create new problems. Why not spend the same amount of time creating educational videos instead on how to use existing tooling that is already readily available?

Other than this rant, I really like gitlab product (we self host at our coding camp) and deploy tokens is a pretty big value add for us for our CI flow.

Edit: Here's a good usecase for the webIDE:

If you see a typo in a comment, for example, you click the pencil icon on that line, which pops open an editor with your cursor on that line, fix the typo, and can create and submit for review a pull request right there. Less than a minute. https://news.ycombinator.com/item?id=16212234

Re: Gitlab 10.7 Released

#16

I implemented the HTTPS-only Pages feature in this release. I just wanted to say that GitLab is a great project to contribute to, with a very friendly and professional community! Definitely recommend to anybody interested in contributing to a project themselves. [1] https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/16273 [2] https://about.gitlab.com/contributing/

> I just wanted to say that GitLab is a great project to contribute to, with a very friendly and professional community!

this. I've had a fantastic experience as well. Its one of those communities and projects that has been so good I have to leave a comment about it :)

Thank you GitLab team and contributors!

Re: Gitlab 10.7 Released

#17
post #15

I wish I could understand the value add of yet another IDE. The whole reason for tech to exist is to improve things around the world, and yet brilliant minds are still spending years building one IDE after another. "Switching branch and remembering branch names..." is a simple git status. On vim, you can get a file browser on the left by using nerdtree plugin, and to write commit messages on the right side you simply…

I've used it a couple of times now not to develop, but to incorporate review discussions and minor other fixes. But from my perspective the true value is for non developers, or when you're starting with Git. No need to worry about remotes and what you did or didn't sync. Or if the branch is even there and you need to set the upstream. Concepts one need to get now are branches and commits. No cloning, fetching, pulling or pushing. When starting, branches and commits are hard enough.

Than, when the new user is comfortable they can work their way up.

Re: Gitlab 10.7 Released

#18
I, for one, am very impressed by the capability of this (mostly-remote, IIRC) team to ship so many releases, so fast. We have now one release per month!

We host most VideoLAN projects on our own instance, and the updates are now very smooth, especially compared to the beginning.

Of course, there are features that we care about a lot and are not implemented, because they don't consider them important (or maybe not worth their time, which I understand) but it's a very solid software. I hope it can replace our wiki and bugtracker soon...

Re: Gitlab 10.7 Released

#19
post #12
post #7

Earlier quoted context omitted.

They have a dedicated section about performance improvements in the release notes. It links to a list of 53 commits from this release targeting performance: https://gitlab.com/groups/gitlab-org/-/merge_requests?scope=...

Thanks Scott for linking to that. We're very much trying to improve the performance of GitLab. I do think that most of our performance improvements are to improve the end-user experience. So I totally understand dijit's request to reduce memory. Today we recommend 4GB of memory to run GitLab https://docs.gitlab.com/ee/install/requirements.html#memory One big thing would be if we can run the Ruby code multithreaded ht…

Are there any plans or targets to lower the memory requirement?

Re: Gitlab 10.7 Released

#20
post #15

I wish I could understand the value add of yet another IDE. The whole reason for tech to exist is to improve things around the world, and yet brilliant minds are still spending years building one IDE after another. "Switching branch and remembering branch names..." is a simple git status. On vim, you can get a file browser on the left by using nerdtree plugin, and to write commit messages on the right side you simply…

There was discussion about this about three months ago, when this feature was first announced:

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

The tl;dr seems to be that in certain environments there's a big benefit to having the ability to browse a codebase and make a quick and simple edit without having to deal with the overhead of git.

Post reply on HN