[Update 20180604 @ 14:00 UTC: Acquisition confirmed. Microsoft is paying $7.5 billion in stock. Coverage at Microsoft, Security Week, The Register, and The Verge. Also, see the Microsoft blog post. --martyb]
Microsoft has reportedly acquired GitHub
Microsoft has reportedly acquired GitHub, and could announce the deal as early as Monday. Bloomberg reports that the software giant has agreed to acquire GitHub, and that the company chose Microsoft partly because of CEO Satya Nadella. Business Insider first reported that Microsoft had been in talks with GitHub recently.
Time to move off GitHub?
Previously: Microsoft Holds Acquisition Talks with Github
An AC also submitted Bloomberg's article.
(Score: 4, Interesting) by VLM on Monday June 04 2018, @03:03PM (3 children)
Eh ... I was motivated enough to check the vmware production image, ours has one CPU, 1.5 G ram (claims 250 megs active, probably doesn't need 1.5 G), 20 G storage, honestly not doing terribly much with not much resources. Its pretty wimpy compared to production servers (DB, etc) but pretty beefy compared to one of the DNS servers or one of the openldap servers. I would say its a solid medium size application.
My understanding of "gitlab on raspberry pi" is its usable, but not fast, although I've never seen it myself.
Most of its optional or OK to ignore. I remember spending maybe two hours getting jenkins and gitlab talking such that jenkins would autobuild and auto-test and auto-deploy to dev images when gitlab got a push, and jenkins would insert build results back graphically into the GUI on gitlab, and it was kinda complicated but all documented online and 100% possible to completely ignore if you don't want to do that kind of stuff. Kinda like MS Office products where the average user ignores 99% of the features but which 99% is ignored seems different for each user. But yeah gitlab is huge and you can spend a week messing with its weirder corners if you treat it like an adventure game RPG in exploration mode.
(Score: 1) by nekomata on Monday June 04 2018, @06:39PM (2 children)
>My understanding of "gitlab on raspberry pi" is its usable, but not fast, although I've never seen it myself.
I ran it on a 2G/2CPU VM for 2 users with maybe 3 small projects at the time, absolutely nothing special. After constant insane slowdowns I set up a cronjob to restart the whole thing every night just to work around the memory leakage. (don't remember the version, but it was 1 year ago, newest version at that time.)
I just killed the VM, never checked to see why it behaved like that (but it was a standard CentOS7 with the standard gitlab community install). My assumption at the time being "that's probably normal behaviour and nobody runs this thing on less than 16G of memory". Given your experiences, maybe I should give it another try.
(Score: 2) by VLM on Monday June 04 2018, @06:54PM
Never ran into anything like that in any location, with about 20 times the use stats you post but lower resources, musta been some kind of bug or config issue. Could be a unique feature thing where you had to enable XYZ for some local reason and XYZ is blowing it up, or some log file is getting spammed.
I once had a problem with a corporate vuln scanner that terrorized every open port 80, even internal use only ones, with roughly 5000 HTTP reqs per day one after another like a denial of service strike. That was annoying.
(Score: 2) by bobthecimmerian on Monday June 04 2018, @08:11PM
We see that at work too, we have a team of ~20 using Gitlab and we have to give the VM 10GB of RAM (with Gitlab as the only thing on it) and kill the process overnight in order for it not to hang. The source code repository is ~ 6GB and maybe 1.5 million LOC, but the speed problems are all in the web UI, clones, commits, and so forth are as fast as always.