Still, good luck to them :-)
Some people (say, big companies) think exactly the opposite because they are after an on-prem solution, and for that Gitlab kicks Github's ass.
Ouch. If you run your own servers already it's financially worth hosting your own gitlab at the minimum price point.
I expect it will be the big orgs who don't move due to integration costs.
That said, I think it's always worth considering using a tool because of their options for the open-source community... github, travis-ci etc have changed the way a lot of people work. GitLab might be what I reach for for self-hosting, but more likely to try the community/open edition first.
Using VSO (VisualStudio.com) for hosting at work, and some of the integration parts are very nice... Though no idea what a private TFS instance costs.
They did a manual Backup before meddling with stuff so they only lost data from a really small timeframe.
CI downtime, on the other hand, is troublesome. I love using Gitlab CI and it didn't take me more than a few minutes to manually deploy what I had to, but I decided I need most of my CI to be controlled by me.
The end result is a simple refactor of my test and deploy specs to their own rake tasks (Could be Bash scriots or whatever) and I'll have Gitlab run a simple gle command, if it goes down I run the command manually...
Now some eventual downtime is not such a deal breaker anymore, and I continue having private repos and CI (Awesome CI) for even the smallest (And private) projects I work on... Not a bad deal if I do say so myself.
GitLab Enterprise Starter is $39/user/year, and GitLab Enterprise Premium is $199/user/year.
$21 is per-month. Per-year that works out to $250/user. If we're going by the month, GitLab's pricing is $3.25/user.
Mozilla does this to great effect:
This doesn't show all the graphs we need to show like 99th percentile request latency but that will come when we add Unicorn support to Prometheus.
It does need to be paired with something that can capture and display the NetFlow data well. But with that, you can literally see what data is going where in your network, accurate to the byte. And with a good visualisation solution, you have the data historically too, so you can (easily) match things up time wise.
eg a developer writes a bad query which pulls 1/2 the database over the network to the front end server for filtering results there, instead of filtering them in the database. You can see that on the network fairly easily, and let the developer self-educate (if given access to the tools). ;)
As an aside, the gold standard used to be a commercial product called "NetFlow Tracker". It was amazing (fond memories), but the company behind it (Fluke Networks) didn't seem to know anything about software sales. So, it's now discontinued. :(
Hopefully there's a modern version of that somewhere. :)
If you would like to follow progress you can dive into it all here [1]. One of the spearpoints is Gitaly, which should significantly improve git access.
[0]: http://monitor.gitlab.net/dashboard/db/fleet-overview?from=n...
[1]: https://gitlab.com/gitlab-com/infrastructure/issues/947
For everything else, I like Gitlab a lot -- it seems to have the best integration of tools of any code host.
I'm also warming to the idea of treating CI as "pipelines", and find myself thinking of tooling more in that way.
I love the integrated CI, though, and the use cases it enables. I love that I can just make a pipeline that lints, tests and compiles my code and then, if all of those pass, ends with deploying it to production.
There are many more Gitlab features I like a lot, and the fact that they're all integrated is icing on the cake.
Can't we be realistic about companies instead of getting wild eyed? You don't have any reservations about recent events?
I haven't seen them promoting that hard as you describe.
I wrote my comment of the pure satisfaction with their services and my use case. So stop being ignorant and be civilized and at least argument what you say. What happened to them month ago was an accident that could happen to many others, but the difference was that they were 100% open about it, with others you may won't even know shit is happening.
Nobody forces you to use anything.
Edit: And now you edit and delete 90% of comment, nice.
(My comment excludes the CI part)
I have. I've installed Gitlab and Mattermost on my own server. Gitlab is great but I found Slack was a better product (over Mattermost). Have you tried installing it?
I created a Gitlab account and was planning on using it over Github but their recent data loss scared me off. Is that unreasonable? It worries me just as much to see them buying a company a month after that. Is slowing down unreasonable?
I want to use Gitlab. I like their open approach, but if people just praise them without being objective about it it doesn't benefit any of us. I might just be a selfish and/or entitled user but you'll forgive me for wanting Gitlab to be good. Don't you?
No, please tell me how you installed a Slack server! (j/k, but it's also kind of the point: GitLab wins on-prem)
Mattermost team here, would welcome any feedback on how we could improve.
Here's a demo of Mattermost features vs Slack as FYI: https://www.youtube.com/watch?v=AKqHWqrAgpk
I had some confusion with the install. It seems the Docker install is favored, but not using a lot of Docker stuff I went with the gitlab-omnibus install on Ubuntu 16.10.
It worked but I didn't feel especially comfortable with it, there were a number of steps. That's vague enough be useless and it could have just been my own ignorance. What is the suggested install if that isn't too basic of a question?
I also had issues with it not liking users sending rather large files but I believe that's an odd use case.
I would use it again but the simplicity of Slack (no setup and no management) won out for now.
"What about Mattermost, how is this different?
Gitter was built to be used in the open. We’ve always seen Gitter as a network, or a place where people can come to connect to one another. Team collaboration, whilst possible, has never been a core aspect of the Gitter experience.
Mattermost is a powerful, integrated messaging product for team collaboration - we will continue to ship and recommend using Mattermost for internal team communication."
They surely have the best intentions. Hopefully one product doesn't take priority over the other and/or they can prevent cannibalization. There's definite overlap.
Edits: typos, wrote from phone.