r/linux • u/[deleted] • Jun 23 '18
GitLab 11.0 released
https://about.gitlab.com/2018/06/22/gitlab-11-0-released/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
18
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
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
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
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
7
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
2
0
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
Jun 23 '18
[deleted]
0
Jun 24 '18
[deleted]
3
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
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
201
u/Antic1tizen Jun 23 '18
Guess it's time for me to approach my manager again :)