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

GitLab 8.9 released

about.gitlab.com

Post reply on HN
Print view View original

31–40 of 63 posts

Re: GitLab 8.9 released

#31

Post by sytse »

lhecker wrote: post #29

Can someone explain me why workers where only alive for 6 seconds? Even now: Why are they only alive for 20 minutes and why is that even acceptable? Is it due to memory leaks? I'd probably instantly lose my job if any of my systems would crash that often without me fixing it, regardless of the reason...

The unicorn workers are leaking memory. Any worker going above a limit will be restarted. Obviously it would be better to reduce the memory leaks further and we welcome help with that. To be clear, it is not a crash, all requests are handled without error to the end user.

Re: GitLab 8.9 released

#32

Post by jakecodes »

allan_s wrote: post #24

Really interesting new features A little feature I'm missing is to have the code coverage percentage in the slack message A bigger one is the fact that the comment text area in code review is terribly slow on my very recent desktop in firefox, and unusable on my cellphone (it used to be ok one years ago) I can't wait to deploy this release (we always wait one week after each release official date, just to let one or…

Thanks @allan_s we are aware of the slowness of the diff tab. It is something we are actively (this very second) working on. I am not aware of the slowness of the text area. Can you create an issue to show us so we can fix it? https://gitlab.com/gitlab-org/gitlab-ce/issues/new

Re: GitLab 8.9 released

#33

Post by connorshea »

juandazapata wrote: post #10

It's fantastic for us that Gitlab keeps putting pressure on Github. I hope they keep this strike for a long time. Having said that, they really must improve the performance. I tried to make the switch from Github to Gitlab a couple of months ago, but the general speed and responsiveness is just below the line. Keep up the good work.

Try again in a few months and it should be a lot better, lots of work has been going into improving performance across the board, e.g. this week we've had two pretty big changes: https://www.scribd.com/doc/316471059/GitLab-Infrastructure-2... and https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/4802 :)

Re: GitLab 8.9 released

#34

Post by connorshea »

darklajid wrote: post #3
ech wrote: post #2

gitlab is gearing up to be the one-stop-shop from development to production. i really like that. unifying the toolset developers and ops have to understand is really a boon for everybody involved. merge restriction as a feature may sound silly, but in my experience, when driving organizations toward CI/CD, especially with "mature" organizations, having the computer say no instead of a human is a major facilitator in…

Isn't U2F a Chrome only feature at the moment? Are you using that seriously already?

Firefox added it ~3 weeks ago under a flag in Nightly, should be in stable a few months from now.

Re: GitLab 8.9 released

#35

Post by allan_s »

sytse wrote: post #30
allan_s wrote: post #24

Really interesting new features A little feature I'm missing is to have the code coverage percentage in the slack message A bigger one is the fact that the comment text area in code review is terribly slow on my very recent desktop in firefox, and unusable on my cellphone (it used to be ok one years ago) I can't wait to deploy this release (we always wait one week after each release official date, just to let one or…

Thanks. It should be possible to have the code coverage in the slack message. Consider opening an issue or contributing the code. The comments text area slowness sounds bad. I've hear people complaining about slowness in Firefox before. I'm not sure how to proceed. Not a bad idea to wait a week after the official release, we expect to have at least one patch release in this timeframe.

https://gitlab.com/gitlab-org/gitlab-ce/issues/19011 https://gitlab.com/gitlab-org/gitlab-ce/issues/19010

here you are :)

Yes I think for most software waiting for the .1 release is mostly safe.

Thanks a lot once again for the deployement process of gitlab, just having to do apt-get update/upgrade is such a wonderful things, most of project should learn from you, as too often in companies you start to freeze at one version, because the upgrade process is too much mind taking and soon nobody remember how exactly one can upgrade it.

Re: GitLab 8.9 released

#37

Post by sdesol »

jwcrux wrote: post #8

How often is File Locking needed? I thought that was one of the beautiful things about Git - merging de-conflicting is not only a thing, but easy to do...

Unless you've worked in Enterprise, you'll be surprised by what is important. And this is actually an important feature, in my opinion.

Enterprise is all about reducing risk and that's because, a screw up can bring down an entire company. There is a reason why they get ISO certified among other things.

In the post, they talk about using locking to signal intent to change, which is also very important in enterprise. In enterprise, you have domain experts and they know if you muck around with a certain variable setting and if the value isn't correct or is just off, it can make their job and others a pain in the ass.

So if you are a domain expert and if there is a trivial way to ensure people don't ruin your day, you'll use it.

Locking is also useful for locking down certain parts of your software, which is something verification would normally insist on.

Mistakes happen and in the open source world, it's a shrug off the shoulder, in enterprise, it translates into loss money.

Re: GitLab 8.9 released

#38

Post by sytse »

allan_s wrote: post #35
sytse wrote: post #30

Earlier quoted context omitted.

Thanks. It should be possible to have the code coverage in the slack message. Consider opening an issue or contributing the code. The comments text area slowness sounds bad. I've hear people complaining about slowness in Firefox before. I'm not sure how to proceed. Not a bad idea to wait a week after the official release, we expect to have at least one patch release in this timeframe.

https://gitlab.com/gitlab-org/gitlab-ce/issues/19011 https://gitlab.com/gitlab-org/gitlab-ce/issues/19010 here you are :) Yes I think for most software waiting for the .1 release is mostly safe. Thanks a lot once again for the deployement process of gitlab, just having to do apt-get update/upgrade is such a wonderful things, most of project should learn from you, as too often in companies you start to freeze at one v…

Thanks for creating the issues!

And you're welcome for the apt-get upgrades, glad they are a good experience for you.

Re: GitLab 8.9 released

#39

Post by sytse »

StavrosK wrote: post #36

U2F support, finally! Although, there's no way to remove a device if I lose it, that sounds like quite the security risk...

Mmm, that makes sense to me, consider creating an issue for this.

Re: GitLab 8.9 released

#40

Post by vamega »

intsunny wrote: post #16
reipahb wrote: post #7

Earlier quoted context omitted.

Isn't that what deploy keys are for? See: http://docs.gitlab.com/ce/ssh/README.html#deploy-keys Deploy keys give read-only access to clone a repository, and they are associated directly with the repository.

That depends on having an SSH keypair. I just want a token for internal only projects.

I don't understand how your token is different from an SSH keypair. Would you explain?
Post reply on HN