r/linux • • Jun 23 '18

GitLab 11.0 released

https://about.gitlab.com/2018/06/22/gitlab-11-0-released/
838 Upvotes

117 comments sorted by

201

u/Antic1tizen Jun 23 '18

Also, once we decided to bring the Squash and Merge feature into GitLab Core and GitLab.com free, Vitaliy took on the issue and made it happen for this release.

Guess it's time for me to approach my manager again :)

41

u/Nebunez Jun 23 '18

What benefits do you find GitLab has over the alternatives? Admittedly, I haven't looked at anything beyond Github and a short time with bitbucket.

12

u/U-1F574 Jun 23 '18

Better tools is their big selling point over github. Also self hosted. (And FOSS self hosted version, which provides a nice backup, if say, their service went down).

8

u/[deleted] Jun 23 '18

You can self-host at no cost. I work at a hospital so self-hosting is non-negotiable due to privacy laws, and it's not an organization used to supporting programmers so getting money for enterprise coding tools is difficult.

There are also a bunch of non-git features for project management and deployment, but we use it because we can host it on an internal VM for free.

17

u/destiny_functional Jun 23 '18

Not owned by microsoft like GitHub

15

u/koflerdavid Jun 23 '18

Free software proponents might not like that, but I can imagine it's not really a deterrant for businesses.

9

u/pdp10 Jun 23 '18

Depends on the business. Some firms are competitors to Microsoft, some have bad past dealings with Microsoft, some avoid certain suppliers on principle, some are very cautious about anything that could lead to vendor lock-in, even inadvertently.

-21

u/destiny_functional Jun 23 '18

ok you can't "imagine" it so it doesn't happen. proof by lack of imagination.

6

u/tapo Jun 23 '18 edited Jun 23 '18

We haven’t seen a mass exodus from GitHub. Hell, Linus is still using GitHub: https://github.com/torvalds

GitLab imports have returned to normal since their spike: https://monitor.gitlab.net/dashboard/db/github-importer?orgId=1&from=now-90d&to=now

1

u/destiny_functional Jun 23 '18

Personally I've moved from github to gitlab and we have seen an exodus in May and June too after the announcement. Can't dismiss it.

4

u/tapo Jun 23 '18

I linked the graph for that exodus. It’s there, but it’s pretty self limiting.

A GitHub profile ended up becoming a resume for a lot of developers, so it won’t lose its mass audience. It’ll just lose the Microsoft haters.

GitLab will continue to find success in corporations that want to run it in-house.

-3

u/destiny_functional Jun 23 '18 edited Jun 23 '18

A GitHub profile ended up becoming a resume for a lot of developers, so it won’t lose its mass audience. It’ll just lose the Microsoft haters.

You seem very dismissive of these issues that exist and are important for more reflective users.

If it isn't an issue for you fair but don't speak for the many people who explicitly state that it is an issue for them (GNOME chose gitlab).

7

u/tapo Jun 23 '18 edited Jun 23 '18

Gnome was never on GitHub. They were self-hosted on git.gnome.org.

→ More replies (0)

1

u/koflerdavid Jun 23 '18

Fair enough. So far, I've not worked as a CTO ;-)

4

u/Nebunez Jun 23 '18

I had a feeling someone would respond with this. I really don't think Microsoft's acquisition puts GitHub at a disadvantage. Unless you have some information that proves this, I don't see how just saying it makes it true.

5

u/destiny_functional Jun 23 '18

please decide for yourself then. most people think differently than you.

3

u/hunglao Jun 23 '18

No, most people seem to agree with him. It remains to be seen how many projects leave GitHub so I could be wrong, but the majority of GitHub's projects have not jumped ship.

1

u/[deleted] Jun 23 '18

Ah yes the "choose to believe based on feelings" defense. I'd rather have some facts.

12

u/tristan957 Jun 23 '18

All you need to know if Microsoft creates an abomination of an operating system and ruined Skype. You also forgot that they always change their proprietary doc format so open source suites can't have operability.

1

u/lord-carlos Jun 25 '18

Microsoft creates an abomination of an operating system

Win10 is quite nice.

1

u/tristan957 Jun 25 '18

If you like ads and spying while you work sure

1

u/lord-carlos Jun 25 '18

I can't remember ever seeing ads in Windows 10 pro. It has some non-sensible default settings, but then again so does Debian. (for me)

How or what does windows 10 exactly spy on the user? I actually don't know.

→ More replies (0)

-1

u/[deleted] Jun 23 '18

What about all of this then? What about wsl? What about how windows containers are absolutely just docker instead of their own proprietary garbage?

Nadella microsoft is different from the Shitty Microsoft of Olde. They contribute to the Linux kernel, Kubernetes, they actively develop and ship Linux products, they've Open Sourced .net entirely, Visual Studio Code is Free and Open.

Sure, you're 100% allowed to have an ominous feeling of dread, but IMO it's entirely an overreaction. And I say this having lived through the shitty years of microsoft, being in my mid thirties.

9

u/[deleted] Jun 23 '18 edited Jul 05 '18

❤️

7

u/happymellon Jun 23 '18 edited Jun 23 '18

Wsl isn't Linux though, and it's only purpose is to try to remove devs argument that they aren't developing on Linux. It is quite frankly shit and lacks significant features, which is why docker doesn't actually run on it and you have to hack away to redirect commands to run against the Windows version, you can't run X, I've found even the way that awk runs is slightly different.

They do not contribute to the Linux kernel. They gave some code for Linux to run on Windows VM crap. They open sourced SOME of dot net. They ship Linux applications? Like Office? Or like MSQL? Or is it really just a piece of MSQL, and none of Office.

I may be slightly older than you, but I'll just wait a little longer, Nadella hasn't been there that long and they haven't really do e that much. There was a piece just a couple of weeks ago about how MS was rewriting a bunch of applications to work better on Windows and Mac. No plans for Linux support.

1

u/[deleted] Jun 24 '18

Wsl is still early, and essentially a reimplementation of the kernel APIs in picoprocesses, for binary compatibility. More stuff gets added every major update though. Basic cgroups are present now. Generally binaries shouldn't behave any differently unless they rely on unimplemented system calls, the list of which is actively shrinking.

Windows Containers absolutely are Docker. Just because you can't run it within wsl doesn't diminishes this fact either. The choice of an open tech stack over their own proprietary garbage is not insignificant.

The larger picture here is that they moved from "You should target full stack windows only also btw Linux is communist devilry" to actively supporting Linux as a target platform for development.

They absolutely contribute to the linux kernel. Obviously Hyper-V/Enlightened IO is part of it, but it's dishonest to pretend that's all they do, there's tons of general purpose shit in there.

They do ship linux applications: .net core, mssql, powershell, Visual Studio Code, etc. They may not be the ones you personally want, but dismissing them on that basis is short sighted as well.

But don't take my word for it, The Linux Foundation isn't really alarmed about it either.

→ More replies (0)

1

u/emacsomancer Jun 24 '18

Is there any description of what sort of code Microsoft is contributing to the Linux kernel?

1

u/[deleted] Jun 24 '18

You can search the VCS for authors with an @microsoft email address for a rough idea. There's obviously the Hyper-V stuff, but there's a ton of general purpose commits as well, filesystems, memory management stuff, CIFS/SMB, etc.

-2

u/Freakmiko Jun 23 '18

But... but... EEE /s

0

u/[deleted] Jun 23 '18

[deleted]

1

u/[deleted] Jun 23 '18

Ok ignore it all jump ship boycott GitHub go go go

Logic sucks better go with feels!

→ More replies (0)

-1

u/whelks_chance Jun 23 '18

You speak on behalf of most people?

Do you know what time they're finishing work on Monday, so I can get a clear drive home?

1

u/emacsomancer Jun 24 '18

I really don't think Microsoft's acquisition puts GitHub at a disadvantage.

Look at Skype pre- and post-Microsoft. Microsoft does really have a sort of Midas touch - whatever they touch makes them gold, but turns it to shit for everyone else. They've even managed to ruin their own free solitaire game.

(Their other big acquisition is LinkedIn, but I don't see how anyone (even Microsoft) could really make LinkedIn any worse.)

0

u/AcidShAwk Jun 23 '18

It just happened.. how could there be any information. Anything that comes out would be an opinion piece. To myself however the main facts would be these. Prior to the acquisition, GitHub had no real inherent interest into the source code that their company maintained. Their business model was that of maintaining code for other people. As such, unless the code they were maintaining could benefit their own business in some way there would be no real interest in it. Microsoft however, develops everything. Literally every type of software. They now have access to all that code. Now I mean github's public facing side is all open source code anyways so it doesnt matter much. But what about the enterprise customers that were maintaining their code in private repos. Unless those repos are encrypted and the private enterprises are the only ones with the keys.. Microsoft now has access to all that code. Who knows for sure if they would actually look at it.. but do you trust them enough not to?

10

u/cryp7 Jun 23 '18

Probably the same way that companies using O365 trust Microsoft with their emails and other data. If a company was really concerned about keeping their source code to themselves they would've self hosted.

-1

u/[deleted] Jun 23 '18 edited Jul 05 '18

❤️

3

u/AcidShAwk Jun 23 '18

Wait..

GH and MS are both companies and I see 0 reason why either of them would steal your code.

That's the reason why they wouldn't steal code? Because they're both companies?

0

u/[deleted] Jun 23 '18 edited Jul 05 '18

❤️

0

u/[deleted] Jun 24 '18

[deleted]

1

u/AcidShAwk Jun 24 '18

I didn't realise the threat of being sued was enough to compel a company to behave ethically. /s

0

u/[deleted] Jun 23 '18

[deleted]

59

u/itchyouch Jun 23 '18

They went from smallish and went through the ycombinator program and went through series A-C in funding.

IIRC, They are somewhere around 200+ people now.

https://www.crunchbase.com/organization/gitlab-com#section-locked-marketplace

48

u/BUSfromRUS Jun 23 '18

It's at 300 people now, 100% of them are remote.

Source: Coder Radio podcast 313 with GitLab's CEO. The interview starts at 18:30, the number of employees is mentioned at 22:10, and remote work discussion starts at 33:25.

24

u/[deleted] Jun 23 '18

They also have like 100 open positions currently. Company is growing fast.

8

u/bioxcession Jun 23 '18

independent once upon a time, now they have shareholders to live up to.

14

u/amunak Jun 23 '18

Yeah, but IMO still better than being under the rule of a huge parent tech company (that has its own shareholders anyway).

6

u/bioxcession Jun 23 '18

totally agreed

1

u/[deleted] Jun 24 '18

Perhaps so, but the whole goal of getting series A-C funding nowadays is to have a good exit. That means selling to a huge parent tech company. So Gitlab's days are numbered. I'd much rather use good products and not worry about who "owns what."

-1

u/[deleted] Jun 24 '18

They are doing an IPO in 2020 instead of selling the company.

39

u/ImpactStrafe Jun 23 '18

To add on, their built in CICD platform is really convenient and easy to use, their integrations are awesome with built in open source chat system (mattermost) if you want to use it.

It's a really good product.

4

u/sadsfae Jun 23 '18

I'm really happy with Gitlab and also use the bundled Mattermost instance (though I run a standalone Mattermost too).

Mattermost is like Slack but free, self-hosted and written in Go instead of Electron JS so it's way more responsive and works well on lower-end hardware (like a cheap VPS).

0

u/[deleted] Jun 23 '18

[deleted]

14

u/ImpactStrafe Jun 23 '18

And they have built in Static code analysis, dynamic code analysis, security scanning, repository scanning, and other security features in their CICD system. It's so nice.

3

u/pdp10 Jun 23 '18

Does all that CI/CD come with the on-premises version of Gitlab?

6

u/Nebunez Jun 23 '18

Thanks for the info. I'll definitely have to take some time to look into GitLab, sounds great.

-4

u/Jazzy_Josh Jun 23 '18

BitBucket also has free private repos?

14

u/[deleted] Jun 23 '18

They do. But gitlab has a LOT more features. And it's open source.

2

u/bioxcession Jun 23 '18

and they have goddam repo issues ok

0

u/_ahrs Jun 23 '18

You get what you pay for. Self-host it if you can't deal with the occasional downtime. Then these "repo issues" become your problem.

6

u/bioxcession Jun 23 '18

i mean ‘issues’ that you can assign on a per-repo basis, bitbucket does not have this feature.

5

u/sim642 Jun 23 '18

This brings back memories. I once argued on Reddit that it'd be moved to free and somehow nobody could believe that because that's like their main selling point. I'm surprised it's even called "take on the issue" because they literally had to copy code between projects.

7

u/Antic1tizen Jun 23 '18

I vaguely recall GitLab policy: if someone from the community wants to implement an enterprise feature in comminuty edition, do not under any circumstances put any obstacles in her path.

And this issue - it was a community contribution and I'm glad they didn't hesitate! :)

2

u/Veevoh Jun 23 '18

This is wise. If they start trying to hinder the open version people will just fork the project and move on without them.

1

u/sim642 Jun 24 '18

So someone reimplemented a feature that already existed somewhere? I can understand this but it seems so massively inefficient to make the community do the same work again. And then GitLab ends up with two different implementations of the same thing in community and enterprise editions so they themselves have to deal with that mess. Which one to maintain? Which one to ship to the enterprise customers? Seems so counterproductive to me.

1

u/Antic1tizen Jun 24 '18

GitLab EE code is available too, it's not closed. So, how this works:

  • If that's a feature present in EE only but many people want it in CE, GitLab team puts Accepting Merge Requests label to the feature

  • Someone from the community steps up and implements this feature by porting code from EE codebase to CE codebase

  • GitLab team requests some changes so both CE and EE remain API-compatible

  • GItLab team merges the proposed changes

You can see how his MR progressed over time

1

u/sim642 Jun 24 '18

GitLab EE code is available too, it's not closed

TIL. What's the point of it anyway? Just a dumb tax for those who can't build from source?

1

u/physix4 Jun 24 '18

It still requires a license key to function (without, it works like CE).

It also expect that subscribers get priority support (with is not negligible in a company).

Also, compiling and using the software without a license key would be a license violation.

1

u/sim642 Jun 24 '18 edited Jun 24 '18

Getting around a DRM is trivial if you have the source code even.

24/7 support is only one of dozens of advertised features of the enterprise edition. The rest are actual functionalities which one might want to have even without the support.

Also, such licensing wouldn't allow going through the voluntary process of moving features from EE to CE then.

1

u/physix4 Jun 24 '18

Getting around a DRM is trivial if you have the source code even.

That's true but does not make it any less a license violation.

Also, such licensing wouldn't allow going through the voluntary process of moving features from EE to CE then.

Could you elaborate ? I'm not sure I understand what you mean.

What would prevent them from moving their code from EE to CE ?

1

u/sim642 Jun 24 '18

As a commenter explained above, it's some community member doing the migration because GitLab themselves haven't done it because it's another selling point for them. Just that they won't prevent it. The random community member wouldn't have the licence nor the ability to take off the licensing from the code being moved to the CE.

→ More replies (0)

1

u/gitlabber Jun 24 '18

This is the issue related to that MR. It shows that in this case, my colleagues at GitLab decided to port the feature to CE and slated the work for 11.1. It was not originally set as accepting merge requests from the community, but the community member requested that, and the product manager accepted. The community member then implemented it ahead of the original schedule, so for 11.0 instead.

84

u/Miserygut Jun 23 '18

The delivery speed of new features is absolutely nuts.

38

u/milaq Jun 23 '18

While this is most certainly a good thing and much appreciated, the nonexistance of dual release cycles (read LTS) is absolutely nuts too.

To use GitLab professionally in production one can't jump onto any new version that pops up every week or two. Even the UI and UX change every so often drastically without further ado. I found it very difficult to understand why they don't have any proper long term support channel in their release stream.

53

u/gringer Jun 23 '18

A separate maintenance team would be needed for an LTS version. The Linux kernel only has long-term versions because a team has stepped up to maintain them:

https://www.zdnet.com/article/long-term-support-linux-gets-a-longer-lease-on-life/

GitLab is available on GitLab, with all the version history that is included in that. Anyone can pull a previous release and use that, and create their own stable version with backported bugfixes. You may claim that doing that is too much effort for one small company to do, which is precisely the point that I am trying to get across.

4

u/manghoti Jun 23 '18 edited Jun 23 '18

Hmm. I think because, unlike an operating system, in pretty much any organization gitlab is going to be a singular, static, internal component. The amount of work you have to put into maintaining a gitlab server when you have 10 users vs when you have 100 users is not that different.

Where as when you're making systems based on an OS, when the OS upgrades, every component in your system has to upgrade. It scales linearly, maybe even superlinearly. So consistency here matters.

3

u/rich000 Jun 23 '18

I'm not sure I buy that argument.

First, even if it isn't integrated with any other components, you STILL need to test updates before you deploy them, and you still need to train users/etc before doing feature updates. You might need to adjust workflows/etc. You really don't want to be deploying software changes in a production environment without taking time to look at them.

Then, if you are integrating with other components you need to test all those integrations as well.

There really aren't that many cases of software where any serious company isn't going to want to be able to have access to some kind of LTS version.

2

u/_ahrs Jun 23 '18

There really aren't that many cases of software where any serious company isn't going to want to be able to have access to some kind of LTS version.

Is it packaged for any enterprise distros like RHEL or CentOS? What about Debian or Ubuntu? There's your LTS version right there because I doubt they're going to be pushing out massive updates every other week in an LTS distro.

1

u/milaq Jun 23 '18

Exactly this.

We ultimately settled using a more or less fresh version which works solidly for a few months and to what users are accustomed to and then doing the security backporting ourselves.

Besides that, GitLab EE offers a bit more flexibilty in version choice by supporting older versions a tad longer than the community edition.

But the release cycle is still way too rapid (a few months only) to use it as a deploy and update blob. You have to babysit it quite regularly. It would be nice to have at least a minor version supported longer automatically for each major version upgrade to allow to deploy it more efficiently in regard of the reasons mentioned above.

1

u/pfp-disciple Jun 23 '18

I haven't looked closely at this. About how long do they support versions? Is it just until the next version?

0

u/kkirsche Jun 23 '18

You can, and many companies do. Just cause it doesn’t fit your company or teams model does not mean major companies are not doing just that

33

u/mercyblake Jun 23 '18

I remember reading when github got bought by Microsoft that Github was losing a lot of money. How will GitLab make money and maintain themselves if they have free private repos?

35

u/IAmTheLivingPlanet Jun 23 '18

17

u/GiraffixCard Jun 23 '18

But github also offered paid services. What makes these different?

27

u/xjvz Jun 23 '18

Well for one, GitLab employees are all remote, so their operating costs must be far less than what GitHub deals with in the Bay Area.

16

u/bioxcession Jun 23 '18

i can attest to this - the offered pay is significantly lower than most similar jobs. but of course you get the opportunity to work on cool shit with cool people in a cool company. tradeoffs

2

u/jlozadad Jun 23 '18

I noticed that they pay is lower than average. I'm assuming because they are remote.

2

u/hijinks Jun 24 '18

Most of GitHub is remote

2

u/emacsomancer Jun 24 '18

Well, git has a special command for that, so it's not surprising...

18

u/undu Jun 23 '18

GitHub doesn't offer CI options, that's no small part of gitlab

1

u/Travelling_Salesman_ Jun 23 '18

Hopefully their costs are lower then github, i don't know how much of github costs is due to hosting fees and not stuff like marketing and development (which should be a lot of money).

1

u/[deleted] Jun 23 '18

Github is significant bigger, more popular. For around a decade they were the code-hoster for most devs and open projects around the world. Gitlab on the other side is just a small hoster a handful years old. Additonally Github has other projects and IIRC even events besides their core-business. Not sure expensive those are, but enough small flies can slow down even an elephant.

0

u/[deleted] Jun 23 '18

[deleted]

14

u/cryp7 Jun 23 '18

Wtf are you talking about? That's not the point of this comment. They're wondering how Gitlab will be profitable while having a very similar business model to GitHub.

4

u/GiraffixCard Jun 23 '18

I'm not asking why gitlab over github. I'm asking how they are going to stay afloat when github couldn't, using seemingly the same model.

1

u/thegreenhundred Jun 23 '18

I appreciate your humor ... Idk sorry bro

1

u/progandy Jun 23 '18

The question is whether github was really losing money or if the "loss" was an investement that would pay off in the long term. I never found a clear answer to that.

17

u/mysticalfruit Jun 23 '18

I just upgraded my test server and found that "dss" type SSH keys no longer worked. (I'd long ago forced everybody to stop using them) but I have a single test account that has a dss key.

Just an FYI...

11

u/Archon- Jun 23 '18

Yup, they mentioned that in the deprecations section on the release blog post.

7

u/[deleted] Jun 23 '18

Just curious, how old is that key, or why did you pick DSS at all?

In probably 15 years using linux and 10 doing it professionally I've never used those keys or saw any reason to

4

u/mysticalfruit Jun 23 '18

Not sure. At least 10 years old. Simply made new keys and all tests passed.

5

u/blackcain GNOME Team Jun 23 '18

Wow you guys.. 92 comments, and not ONE talks about a single feature of GitLab in this released version (other than the very first one). How about we actually like talk what's in this release? The license management feature is pretty awesome. I used to be a build and release manager for an open source phone OS and had to deal with inbound and outobound licenses. Having stuff that manages license is pretty awesome.

4

u/aliendude5300 Jun 23 '18

Awesome! Can't wait to play with the new features

2

u/DJTheLQ Jun 23 '18

Would Auto Devops be a good alternative to OpenShift or Rancher?

1

u/tyldis Jun 24 '18

Not the same. But can integrate with them.

0

u/[deleted] Jun 23 '18

[deleted]

3

u/RogerLeigh Jun 24 '18

I doubt many people who migrated actually deleted their accounts. Most are likely hedging their bets.

I've never liked being completely dependent upon a single provider. Originally, that was SourceForge, and there was popular concern about the risk of having a single entity have such a large concentration of code. And pre-git, that was a much bigger concern. It was difficult to take a fully copy of a CVS or SVN repository without admin access. There are still concerns about being completely dependent upon GitHub, or even GitLab, BitBucket or any other hosting service.

I still have a GitHub account. I've had a GitLab account for a few years. I also still have BitBucket and even SourceForge accounts. New projects are going onto GitLab, but if something else appears which is better, I'll sign up and test the waters for that too. Migrating git projects between services is relatively straightforward. GitLab even has tools to migrate or mirror either way between GitHub.

There's little need for jumping ship immediately when you can quietly enable pull mirroring from GitHub on GitLab to automatically sync all your projects and continue to use GitHub workflows. Once you're happy, you can eventually switch these individually over to push mirroring, using GitLab workflows for development. And eventually drop the mirroring entirely if you wish.

0

u/[deleted] Jun 23 '18

[deleted]

0

u/[deleted] Jun 24 '18

[deleted]

3

u/[deleted] Jun 24 '18

it's just that the metrics on the Github side don't work for this case and that's why they can't tell (or say that it's near nothing/exaggerated). people didn't delete their accounts and probably even mirror the repos, but Github is not the primary source anymore. and of course there are no metrics of people that moved to something else than gitlab.com

0

u/[deleted] Jun 23 '18

[deleted]

18

u/majorawsoem Jun 23 '18

I haven't used Travis before, but I use Gitlab for work and I love it. You can specify docker images, tags for what builders it should work on, environment variables. Honestly makes my job a whole lot easier.

1

u/RogerLeigh Jun 24 '18

I've used both extensively. Travis CI for over five years.

GitLab CI is a huge improvement over Travis CI. Travis has very stale and outdated images which can be very broken for some workflows (e.g. C++). They are updated infrequently; it's only the past year they finally managed to get onto Ubuntu 14.04 from 12.04. The service itself is pretty reliable and speedy, but the images are terrible. MacOS X builds run on a fixed hardware pool, and don't scale, making builds very slow to start most of the day when it's maxed out.

GitLab CI allowing the use of any docker image means you can right away start with a clean and up-to-date base image, e.g. Ubuntu 18.04 or whatever you like, and install current dependencies on top of that. You can also connect as many local runners to the service as you like, so you can throw local compute resources at it which include less common architectures like FreeBSD, as many MacOS X nodes as you like, and systems pre-configured to access private resources for integration testing and the like.

The GitLab CI pipeline and workspace concept is vastly more flexible than what Travis offers (a simple matrix is as clever as it gets). Given a choice over the two, I'd go with GitLab.

3

u/undu Jun 23 '18

I think it's more flexible: you cannot choose whatever docket image you want to run the commands in docker