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

GitLab 8.5 released

about.gitlab.com

Post reply on HN
Print view View original

211–220 of 246 posts

Re: GitLab 8.5 released

#211

Post by [deleted] »

hinkley wrote: post #205
yapdoggydog wrote: post #166

Earlier quoted context omitted.

Hey, Kelvin from Atlassian here. We are pretty flat out ourselves improving both Bitbucket Cloud and Server. I can see how SSO isn't terribly important if Bitbucket is the only one of our products you use, but it's critical for our customers who co-own Bitbucket and JIRA (or Confluence, or HipChat, etc.). It was a fairly massive undertaking: retrofitting auth across our portfolio of products took some serious enginee…

Honestly, I don't know why you didn't have SSO years and years ago. You encourage crosslinking between products that have distinct session lifetimes, I feel like I spend all day typing in my password again. (Also, can you take the fucking 'remember me on this machine' button away? It's a cruel, cruel tease. It has not worked a single time on 4 different installations I've had accounts on over the years)

[deleted]

Re: GitLab 8.5 released

#212

Post by manyxcxi »

geofft wrote: post #187
chrisseaton wrote: post #176

Earlier quoted context omitted.

> All developers start out as free software developers, then gain employment. I don't think that's true. Some people never get involved in free software even as a hobby. Some people get apprenticeships and learn to program from scratch on the job.

Or, strange as it may seem, they learn how to write software from a four-year college degree. And colleges are notoriously bad at teaching so much as source control, let alone what source control options are there, how to use a bug tracker, etc. (Which makes sense, because you don't strictly need source control if you aren't collaborating heavily, and you don't need a bug tracker if you have a single development week…

Seriously... My favorite was in a lower level DB class we had to write, basically, a small PHP app connected to MySQL. On the first day of class the instructor stressed this class was about databases, not PHP, and would basically just cover getting a connection going and the rest was up to us. I think having been doing development and getting paid for it via 'internships' at various companies when I was younger really made me a better, but angrier student in my college CS days. On the one hand, I needed zero time to get up to speed on C, C++, Java, and PHP syntax so I could focus on the algorithms and other topics being taught. But I doing so it became very clear that I was going to the real world and most of this stuff wasn't coming with me.

Re: GitLab 8.5 released

#213

Post by tedmiston »

sytse wrote: post #190
tedmiston wrote: post #156

Earlier quoted context omitted.

That would be nice. In GitLab today, we end up deleting and re-creating merge requests, or waiting until comments "@ ready for merge".

Why do you need to do that? Have you looked at the merge request approvals feature https://about.gitlab.com/2015/07/29/feature-highlight-merge-... (EE/.com only)?

It's not about the number of approvers (just one), but more the approver knowing that the submitter is done making revisions. Usually after the first merge request, we do code review then wait for revisions, that's when the tag happens.

Now this would be awesome:

> We’re thinking about more improvements to the Merge Request Approvals, the main improvement being automatic suggestions for reviewers, based on the history of the changed files in the merge request. For instance, if Jane worked a lot on a certain class and you submit a change to that class, Jane gets suggested to approve your merge request.

Today we are using the self-hosted community edition though.

Re: GitLab 8.5 released

#214

Post by VonGuard »

developer2 wrote: post #157
Afforess wrote: post #150

Earlier quoted context omitted.

That's a poor strategy. All developers start out as free software developers, then gain employment. I persuaded my work to purchase Gitlab EE licenses, due to ease of use and it's excellent features & support. I can't imagine I'd say the same of Atlassian products. Capture awareness / interest early.

You'd be in the minority. Correct me if I'm wrong, but I'd bet you're at a small company where a low-level employee's opinion was taken into account when making the decision of which product to use for 10-50 people. In medium to large sized companies, Atlassian will usually win out when you have a CTO that manages 100+ developers. Enterprises really like to stick with the "safe bet", where there are expensive license…

It's so funny that this is the way it's become, as Atlassian grew up being the cheaper, simpler alternative to extremely expensive, super opaque, ultra closed source systems like Clear Case. I remember a time when Atlassian actually raised the prices of Jira's top level of support and service because enterprise CTOs were confused by such a low price point.

Re: GitLab 8.5 released

#215

Post by x1024 »

dogweather wrote: post #133
x1024 wrote: post #113

Earlier quoted context omitted.

"GitHub failing hard". GitLab is great, but it's kind of a copycat project. Nothing wrong with that, it's just there really isn't a compelling reason to join beyond "less-predatory pricing". And the people who care about that use private repos, not OSS.

> predatory pricing I've always thought GitHub's pricing is awesome and very accessible. Can you explain?

Suppose you are a web agency. Every single project for every single client should be version-controlled, right? But that tends to quickly add up when using GitHub - about a dollar per project per month.

So, if my company finishes 30 projects per year, we'd be paying $360/year to GitHub for what is essentially "storing a backup". And if we do this every year, that's $1000/year within 3 years. Not to mention that for "Organizations" the prices are doubled. For some reason. So... $2000/year?

Right now the same job is done by a $5/mo linode, with the prospects of upgrading to $10/mo.

Re: GitLab 8.5 released

#216

Post by mrmondo »

sytse wrote: post #198
mrmondo wrote: post #149

Earlier quoted context omitted.

Have you tried running GitHub EE on something of the same spec? It's terrible to near impossible and it doesn't include nearly as many of the features as Gitlab. We have been running Gitlab for 100~ employees for well over a year on a single, medium/low specced VM and its lightning quick, so much so that when Devs/Ops have to use GitHub you can hear the sighs around the office!

Glad to hear GitLab is fast for you! Will be even faster with 8.5 :)

Seriously Sytse, Gitlab has not only continued to improve, it's done so at rockets pace while (and here's the hard part) at the same pace also improved quality and test coverage.

Do you remember a year or so ago when I was whinging about some regressions after several upgrades? Well I'll tell you what - there hasn't been any that have impacted us in such a long time upgrades - even to a major version - do not worry me one bit and our Devs are always excited to see what's new.

I'm not sure if you remember but we're a non-profit, charitable organisation and GitLab has really helped us immensely over the past year.

A damn fine product from a damn fine team, supported by a damn fine community.

Re: GitLab 8.5 released

#217

Post by elygre »

sytse wrote: post #142
dogweather wrote: post #132

Earlier quoted context omitted.

GitLab has a ton of strengths, but still has large weaknesses in the area: gitlab.com implementation and design. gitlab.com is the public 'demo' version which people compare to github. It's missing a few key items that would make it appealing to open source developers (and that I'd like to see them prioritize.) E.g.: * Site search. It's been broken for months or possibly years. (Response time > 45 secs., Relevancy is…

I agree we can do a lot better in project discovery on GitLab.com. I do want to mention that https://gitlab.com/explore?utf8=%E2%9C%93&filter_projects=gi... gives results in a few seconds and GitLab itself is the first hit.

For an in-house installation, it would also be useful to have an editable front page of some sort. Here, you could publish notable projects, or perhaps the ones most sought after. It would also be a channel for news, faqs, etc.

I created an issue at https://gitlab.com/gitlab-org/gitlab-ce/issues/13239.

Re: GitLab 8.5 released

#218

Post by ayufan »

tdkl wrote: post #180
jobvandervoort wrote: post #46

Earlier quoted context omitted.

Thanks! Should be soon!

Will there be a possibility to use an apex domain ? Looking to switch from GH Pages.

Yes. Sure. Instead of adding the CNAME you need to add an A record. You can get the IP address with dig: $ dig a myuser.gitlab.io

Then configure your domain to point to that IP address.

We are currently working on documentation covering that part too.

Re: GitLab 8.5 released

#219

Post by jschumacher »

X-Istence wrote: post #167
Afforess wrote: post #150

Earlier quoted context omitted.

That's a poor strategy. All developers start out as free software developers, then gain employment. I persuaded my work to purchase Gitlab EE licenses, due to ease of use and it's excellent features & support. I can't imagine I'd say the same of Atlassian products. Capture awareness / interest early.

Yep. I got my work to purchase EE license for Gitlab because it's miles ahead of Bitbucket Server.

Would love to hear what features in your opinion but Gitlab miles ahead of Bitbucket Server.

Re: GitLab 8.5 released

#220

Post by dblessing »

nrclark wrote: post #60

Was 8.5 able to address either of these? Large commits can't be viewed: https://gitlab.com/gitlab-org/gitlab-ce/issues/10785 Users created via LDAP login continue to count towards the user-count even if the LDAP account is deleted: https://gitlab.com/gitlab-org/gitlab-ce/issues/11844

In EE there is a nightly LDAP sync worker that will auto-block any LDAP users that are no longer in the directory. This should address the active user count issue for licensing.
Post reply on HN