81–90 of 356 posts
As always, we're happy to answer any questions about GitLab.
Heroku offers automatic deploy on linked repos from GitHub. Do you plan to integrate with Heroku to offer similar feature?
However, you can already deploy from GitLab quite easily to Heroku, it just requires a single line in your CI config:
http://docs.gitlab.com/ce/ci/examples/test-and-deploy-ruby-a...
Earlier quoted context omitted.
I'll leave the marketing talk to less biased people here, but do note that: - you can use GitLab.com for free: unlimited public and private repositories, unlimited collaborators, free hosting of your Docker images, free hosting of your static site with any static site generator and free CI / CD - GitLab CE is fully open source (MIT Expat). You can easily install it anywhere you want.
"you can use GitLab.com for free" It seems like that is the main selling point. However, I think that most of us don't want the extra weight of managing yet another tool. Thus why many of us use GitHub to begin with and not something else...
I love how responsive our local (departmental) instance of GitLab CE is -- it's downright snappy compared to the corporate instance of JIRA. We love the issue tracking subsystem of GitLab and use it as our main ticketing system. We've done a few talks on Git basics to help increase adoption, and are doing a free webinar "Git Foundations: Basic Concepts and Definitions" next week: https://www.eventbrite.com/e/git-foun…
If you plan on doing physical events, drop me an email (job at gitlab).
Earlier quoted context omitted.
Was over a year since I last used GitLab, and I wonder if the resource usage and response times of a self-hosted instance has improved? Back then we were 3 developers having roughly 20 repos. The memory usage was over 2GB when idle and response times were at best between 2-3 seconds. Testing your hosted version, loading this page[1] for example takes 4 seconds (3.6s TTFB). Don't get me wrong, the platform and its fea…
They've done a lot of work on performance in the past year. I'd recommend taking it for another spin.
https://tools.pingdom.com/#!/cOKg2F/https://gitlab.com/gitla...
But it is the one and only feature i am missing so not worth upgrading to EE for me.
As soon as an alternative (open source, self hosted, free) comes around that does have this built-in, i will be tempted to try it. (and of course on success i will move away from gitlab).
But for now, gitlab (CE) works best for me, self hosted.
As always, we're happy to answer any questions about GitLab.
Was over a year since I last used GitLab, and I wonder if the resource usage and response times of a self-hosted instance has improved? Back then we were 3 developers having roughly 20 repos. The memory usage was over 2GB when idle and response times were at best between 2-3 seconds. Testing your hosted version, loading this page[1] for example takes 4 seconds (3.6s TTFB). Don't get me wrong, the platform and its fea…
GitLab.com is slow, occasionally painfully so. We're very aware of that and are working to improve that. You're welcome to watch or contribute here [0].
We moved from BitBucket on premise to GitLab CE on premise. Actually most things now just works. Updating is a breeze. Instead of downloading a installer and copying / fixing server.xml we can just do a apt update && apt upgrade -y. Some things are a little bit akward but BitBucket didn't had this, too: - FF only merges is only EE (too bad that would be a really major selling point even for CE, squash button would be…
Do you have more examples of workflows we are not supporting at all or well enough?
> - Artifacts API is limited to everything or nothing
Right you are, you might want to track this issue[1].
> - CI Stages can be defined as trigger only but you can't have multiple triggers that starting different things (considering a production trigger and a testing trigger while you don't want the 'manual' thing directly in GitLab, especially when integrating into other systems makes this a flaw)
I don't fully comprehend what you mean, could you elaborate?
Earlier quoted context omitted.
They've done a lot of work on performance in the past year. I'd recommend taking it for another spin.
Not enough, apparently. That page takes 10.5s to load and fails several performance metrics. https://tools.pingdom.com/#!/cOKg2F/https://gitlab.com/gitla...
GitLab.com is too slow. We're working on it here: https://gitlab.com/gitlab-com/infrastructure/issues/59
I really liked Gitlab when last I tried it, but in the end I went with https://gogs.io/ instead. For a small-ish team this felt like the most straight forward self-hosted solution. Still missing LFS though, which sucks, but it's being worked on.