GitLab 8.9 released • Hacker News Board

Re: GitLab 8.9 released

#11

Post by iBotPeaches » Wed, Jun 22, 2016, 7:36 PM UTC

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...

It looks like its more intended for asset files like PSDs and more where Git conflict management isn't as helpful.

Re: GitLab 8.9 released

#12

Post by sytse » Wed, Jun 22, 2016, 7:45 PM UTC

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.

Thanks. We are the speed of GitLab.com is below the line. As you see in the post we're working hard to make it better. Performance of single tenant GitLab installations should be good already.

Re: GitLab 8.9 released

#13

Post by sytse » Wed, Jun 22, 2016, 7:46 PM UTC

iBotPeaches wrote: post #11

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...

It looks like its more intended for asset files like PSDs and more where Git conflict management isn't as helpful.

Exactly, it is for files that can't be merged because they are binary instead of text based.

Re: GitLab 8.9 released

#14

Post by sytse » Wed, Jun 22, 2016, 7:48 PM UTC

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…

Thanks for your kind words. We indeed want to be the one-stop-shop from idea to production. For the complete scope see https://about.gitlab.com/direction/#scope

Re: GitLab 8.9 released

#15

Post by ech » Wed, Jun 22, 2016, 8:13 PM UTC

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 has a plugin that works fine from what i've heard from the others. i still rely by default on totp for generic dual factor auth, since i can provide already working solutions from web to ssh authentication. however, yes for web applications, some clients went the u2f options, and the users overwhelmingly prefer it. since u2f is getting very quickly traction in products (case in point, gitlab) and the user experience is so simpler for a similar level of security, it'll probably become my go to in the near future.

Re: GitLab 8.9 released

#16

Post by intsunny » Wed, Jun 22, 2016, 8:15 PM UTC

reipahb wrote: post #7

intsunny wrote: post #4

Will repo deploy tokens ever be a thing? I would like read-only deploy tokens associated to a repo, and not a user. I just don't like having to create dummy users with repo access to generate deploy tokens.

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.

Re: GitLab 8.9 released

#17

Post by Jack5500 » Wed, Jun 22, 2016, 8:23 PM UTC

I really like GitLab, but again like with the last release there is no Raspberry Pi 2 package. Even though it's officially supported platform it lacks behind over 2 minor versions by now (8.7.7).

Re: GitLab 8.9 released

#18

Post by Keats » Wed, Jun 22, 2016, 8:24 PM UTC

Is there a .travis.yml -> .gitlab-ci.yml conversion tool in the work? It's the only thing preventing me from switching to gitlab really

Re: GitLab 8.9 released

#19

Post by d33 » Wed, Jun 22, 2016, 8:40 PM UTC

Thanks for yet another very smooth upgrade! I even forgot to back up the server and I have nothing to regret. I just hope that you'll fix this one tiny UI problem I noticed:

https://gitlab.com/gitlab-org/gitlab-ce/issues/19004

Other than that, I'm perfectly happy. I love the progress!

Re: GitLab 8.9 released

#20

Post by ech » Wed, Jun 22, 2016, 8:41 PM UTC

sytse wrote: post #14

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…

Thanks for your kind words. We indeed want to be the one-stop-shop from idea to production. For the complete scope see https://about.gitlab.com/direction/#scope

yeah i read the scope. but since the border between scheduling, configuration management, monitoring etc... is extremely blurry, with a high number of interconnection between systems, and lacking any kind of standard contract between them, i'm more wary about the introduction of these features.