20 ms·

GitLab 8.5 released

603 points by doubleg 11y ago

jobvandervoort 11y ago
We're super excited with GitLab 8.5. It's much faster, no matter the size of your instance (but especially for larger instances). The Todos, ability to revert commits and CNAME support for Pages, are things that have been much requested and we're happy to have now. As always, we're here if anyone has any questions about anything.
- gpc 11y ago
  https://gitlab.com/gitlab-org/gitlab-ce/issues/11489 https://gitlab.com/gitlab-org/gitlab-ce/issues/11489 Didn't make it in?
  - jobvandervoort 11y ago
    It seems not, unfortunately, I'm sorry if you were waiting for it. I'll discuss if we can ship it in a patch [0], otherwise it'll land in a month in CE. [0]: https://gitlab.com/gitlab-org/gitlab-ce/issues/11489#note_3857097 https://gitlab.com/gitlab-org/gitlab-ce/issues/11489#note_38...
    - gpc 11y ago
      Thanks, Looking forward to it. otherwise, congrats on another release!
      - jobvandervoort 11y ago
        Thanks! Consensus seems to be we can ship it somewhere this week.
        gpc 11y ago
        I've been keeping an eye on that issue thread throughout the morning and although it doesn't seem appropriate for me to make a comment over there just to say this, I wanted to communicate it somewhere: the gitlab team is really impressing me in terms of responsiveness and flexibility. I really hope to see you keep that culture as you continue to grow and succeed. It doesn't go unnoticed!
        sytse 11y ago
        Thanks, glad to hear that. We're doing everything we can to keep and improve upon that culture. Being remote first and having a public issue tracker certainly helps, less difference between a comment of a co-worker and of a user.
- fsiefken 11y ago
  Hi Job, does this mean it is also faster in low memory environments like 512M? ToDo integration is a great feature!
  - sytse 11y ago
    No, unfortunately not. We recommend 2GB of memory to run GitLab https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/install/requirements.md#cpu https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/inst... If 512MB is a requirement for you please consider using Gogs. Glad you like the Todos feature!
    - tshannon 11y ago
      I just wanted to say how awesome it is that you mention Gogs, a competing platform. It shows that you're focused on your domain, not closed-mindly discounting every competitor, and are open about any shortcomings in Gitlab.
      - sdesol 11y ago
        It also makes sense from a business point of view. The three strong points that I've taken from business school are: 1) You can overtake an incumbent if you can offer twice the value at half the price. If you can produce a drill that works two times better than existing drills at half the price, you'll overtake the drill market. 2) You can't compete with "as good as". Winning here is more marketing than anything and this is where companies like Apple and Coco-Cola shine. You can't beat Coke with point one, since it is impossible to produce something that is better than Coke. You can measure the performance differences between drills, but you can't measure the psychological value of Coke and Apple 3) You can't compete by price, unless you are dealing with a commodity product, which brings me to my point for posting. Turning "Git hosting" into a commodity product is not a bad situation for GitLab and I honestly think this is where it's heading. In a year or two, we'll probably see less tangible/understood things become the main selling point. Such as intelligent code reviews, better code management metrics, defect predictions and so forth. Edit: Forgot to mention that point 3 is also where Atlassian deserves a lot of credit. They are leveraging point 3 and trying to parlay it into point 1.
- eadz 11y ago
  Pages are an EE feature, but one which is useful for open source projects. Would you accept a pull request for a community implementation of Pages? or would a fork be needed in this case? How do you see this sort of issue playing out?
  - ywecur 11y ago
    This is a very good question and something I'm always concerned about when it comes to open core products.
  - sytse 11y ago
    Good question, how we deal with that is detailed on https://about.gitlab.com/about/#stewardship https://about.gitlab.com/about/#stewardship Please let me know if you have any questions.
- dogweather 11y ago
  Have you deployed it to gitlab.com?
  - sytse 11y ago
    Not yet, from the OP: "For GitLab.com users: We plan to enable custom domains on GitLab.com in the following week, so stay tuned!"
- orless 11y ago
  Can it be that GitLab pages are down? I'm getting 503 at the moment: * http://gitlab-examples.gitlab.io/pages-plain-html http://gitlab-examples.gitlab.io/pages-plain-html * http://gitlab-examples.gitlab.io/pages-jekyll http://gitlab-examples.gitlab.io/pages-jekyll * http://www.downforeveryoneorjustme.com/http://gitlab-examples.gitlab.io/pages-jekyll http://www.downforeveryoneorjustme.com/http://gitlab-example...
  - sytse 11y ago
    Sorry about that. There was a brief interruption to GitLab pages while we fixed a vulnerability. It is back now https://twitter.com/gitlabstatus/status/701897151790653440 https://twitter.com/gitlabstatus/status/701897151790653440
- hinkley 11y ago
  Is this release going to make any significant difference on the hosted projects? The last time I asked about Gitlab.com in a thread people mentioned that it's not more popular due to performance issues.
  - sytse 11y ago
    Yep, so that is what we solved in this release. Title of the OP: "GitLab's fastest release ever". For more details see the announcement and https://gitlab.com/gitlab-com/operations/issues/42 https://gitlab.com/gitlab-com/operations/issues/42
pilif 11y ago
Nitpick: > GitLab no longer loads large Git blobs (e.g. binary files) into memory when browsing a Git repository. This prevents timeouts and memory leaks. Nope. Not loading something doesn't prevent memory leaks. It might make existing leaks not as bad (because you're leaking less). Either you're not leaking at which point it doesn't matter how big the thing you load is, it will get freed once it's not used, or you're leaking at which point, yes, if you only load small things, you get to run for a longer time before you die, but you will still die eventually. Only loading smaller things doesn't plug leaks. Aside of that: This looks like a very impressive release. Congratulations!
- jobvandervoort 11y ago
  Thanks for the nitpick, always welcome. I'm asking the author of the change what the background is on this. Will update the post if I can be more accurate. Thanks! UPDATE: Technically we're not fixing the leak, but this fix is reducing the impact significantly.
- Ensorceled 11y ago
  Nitpick on the nitpick. If the Git blobs were the source of the memory leak then this would, in fact, fix the memory leaks. Pretty aggressive stance when you may, in fact, be wrong.
  - pilif 11y ago
    > If the Git blobs were the source of the memory leak then this would, in fact, fix the memory leaks. no. Because they are still reading git blobs - just only for the smaller files. > GitLab no longer loads large Git blobs (e.g. binary files) into memory [emphasis mine] So if their handling of Git blobs is leaking memory, then not reading the bigger blobs just gives them more leeway before they crash.
    - Ensorceled 11y ago
      Again, you may still be wrong. Many systems have different strategies for large blobs vs. small blobs (I know it's many because I've written several myself) including chunking strategies, separate memory pools etc. I'm taking this stand because I've had the exact issue we are arguing about: my large file handler had a leak in the memory pool for large blobs. Basically it was shared memory space for multiple processes so large objects could be passed out of band instead of using IO.
fweespeech 11y ago
> With GitLab 8.5, we’re offering GitLab Geo as an Alpha to all our Enterprise Edition customers. Once GitLab Geo has left Alpha / Beta state, a special license will be required to use it. I'm not sure I like this trend. While I understand some features GitLab may feel its worth a "second license" fee, it sets a bad precedent. Similarly, I don't want to give you $390/year for a GitLab instance with 2-3 users which keeps me from paying for the stuff I use for sideprojects. Although, tbh, if you are going the secondary license route for various features it seems I'm better off looking into an alternative and just implementing them myself. I honestly was just using the post-receive hook, etc. for this sort of thing.
- akerro 11y ago
  afaik there will be possibility to get a license for n users instead n*10 packs.
  - jobvandervoort 11y ago
    That's correct.
    - lars_francke 11y ago
      Thanks for that. Can you give us details on when this change will happen?
      - jobvandervoort 11y ago
        We're not sure yet when it will happen, but we'll make it clear when we do. Update: our aim is before Q1 ends.
        lars_francke 11y ago
        Great, thanks for the update.
- jobvandervoort 11y ago
flashm 11y ago
I've moved all my private repos to Gitlab based on the chat on here and other places recently RE Github, Gitlab, and other solutions. I'm very happy overall, the interface is great. It's a bit slower than github currently (the web interface) as I'm using the online version rather than self hosted, but apart from that it's really bloody good. I'll be recommending it to others going forward and using it for all new repos that I want hosted.
- jobvandervoort 11y ago
  Thanks, that's good to hear. We're working hard on making it faster, this release being a major milestone in that work. Last release, we started shipping a performance monitoring tool [0], to make it easier to see what exactly is slow. [0]: https://about.gitlab.com/2016/01/22/gitlab-8-4-released/ https://about.gitlab.com/2016/01/22/gitlab-8-4-released/
  - flashm 11y ago
    Nice, I'll take a look.
  - sytse 11y ago
    Yep, also see our 'Make GitLab.com fast again' issue https://gitlab.com/gitlab-com/operations/issues/42 https://gitlab.com/gitlab-com/operations/issues/42 for updates about performance.
- NDizzle 11y ago
  What procedures did you follow to move your private repos over? I have been using private, self hosted git for years now. Were you able to move things over and keep commit history? (since I guess that's the only feature I currently have.)
  - jobvandervoort 11y ago
    If you move your repository by importing it (in GitLab UI, under new project) or just by clone + pushing it yourself, you will always retain your entire commit history.
d33 11y ago
Two releases ago, updating was a bit of a pain for me, so I guess I'll wait until Friday with this one. Anyway, the new features sound really good!
- jobvandervoort 11y ago
  What was painful exactly?
  - eknkc 11y ago
    First upgrade for me (8.4 -> 8.5) On a pretty small instance (1.7g ram google cloud) + 1gb disk swap the omninbus update failed with out of memory. Added some more swap space and it finished fine. It's probably not powerful enough to run it though.. Just a heads up.
    - jobvandervoort 11y ago
      I'm sorry to hear that. We advise a minimum of 2gb of ram, so I'd expect it run successful for you. I created an issue on the omnibus issue tracker about the memory requirement for upgrades, here: https://gitlab.com/gitlab-org/omnibus-gitlab/issues/1135 https://gitlab.com/gitlab-org/omnibus-gitlab/issues/1135 I'm glad you managed to solve it, though.
whitenoice 11y ago
Impressive release! Is there a guide on migrating from install from source to using omnibus? We currently upgrade from source but would like to move to omnibus.
- jobvandervoort 11y ago
  Thanks! To upgrade from source to omnibus: https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc/update/README.md#upgrading-from-a-non-omnibus-installation-to-an-omnibus-installation https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc... To see all our update guides: https://about.gitlab.com/update/ https://about.gitlab.com/update/
- iBotPeaches 11y ago
  Warning as someone who just did that. MySQL is EE only on Omnibus. I switched from Source (MySQL) to Omnibus only to find that MySQL was EE only. So I had to go back to Source.
  - sytse 11y ago
    You are correct, we only ship our Omnibus packages with PostgreSQL. And the ability to use an external MySQL server is only in the Enterprise Edition. Switching away from MySQL might not be an option for you but documentation on how to convert from MySQL to PostgreSQL can be found on https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc/update/README.md#upgrading-from-non-omnibus-mysql-to-an-omnibus-installation-version-68 https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc...
  - grokys 11y ago
    We recently switched from a source package using MySQL to the omnibus package and the migration to Postgresql was really easy and went without a hitch.
    - sytse 11y ago
      Glad to hear that, we try to keep the conversion instructions up to date and have tested them extensively.
palidanx 11y ago
I just upgraded and the diffs are WAY faster now. Thanks so much for all of the hard work!
- jobvandervoort 11y ago
  That's great to hear. It's a big community that makes this happen.
  - palidanx 11y ago
    Just curious, were there any new changes made to branch creation and protected branches? I'm getting a Branch creation was rejected by Git hook When trying to create branches via my gitlab instance and it seems to take a lot longer to process the request. Pushing via a command shell seems to work well. --update I just rolled back my version to the older version and see that all of the branch functionality via the gitlab site works okay.
    - sytse 11y ago
      I'm not aware of any changes that would explain that error, but that doesn't mean it can't be a regression in 8.5. If so please open an issue for it and link from https://gitlab.com/gitlab-org/gitlab-ce/issues/13350 https://gitlab.com/gitlab-org/gitlab-ce/issues/13350
branchly2 11y ago
When I go to github, there's a search bar at the top to search for the public repo I'm looking for. I can't find the search feature at gitlab.com. How do I search for users or public repos of interest at gitlab?
- jobvandervoort 11y ago
  Use explore to search for interesting projects (and the people that have them in their namespace): https://gitlab.com/explore https://gitlab.com/explore Press `s` to search for anything. However we only support search for people in places where you immediately need them, like when adding to a project. I created a feature proposal to also search through people: https://gitlab.com/gitlab-org/gitlab-ce/issues/13672 https://gitlab.com/gitlab-org/gitlab-ce/issues/13672
  - branchly2 11y ago
    Ok. I followed the Explore link, but I cannot find the search field on that page. It seems to only allow me to browse by trending/most-stars/all. Hitting 's' key on my keyboard doesn't seem to change the page in any way. Am I missing the search field? (Note, this is using Firefox/Iceweasel 44.0.)
    - audessuscest 11y ago
      I think you must be logged in to see the complete UI (with search field)
      - haynes 11y ago
        Indeed. The search field is currently only displayed for users that have logged in.
        sytse 11y ago
        Thanks, that doesn't make sense so I made an issue to remedy it https://gitlab.com/gitlab-org/gitlab-ce/issues/13676 https://gitlab.com/gitlab-org/gitlab-ce/issues/13676
ausjke 11y ago
Still using redmine + gitolite here but have been watching Gitlab for a while, in fact I tried it yesterday and it's still quite resource hungry and slow(using DO's default installation with 1GB memory). Redmine+Gitolite has nearly everything I need but Gitlab's code view interface is better. Redmine's backend seems running more efficiently but its interface is not modern enough at this point, especially on how to review git repos.
- dijit 11y ago
  gitlabs minimum requirements are 2G of ram (although that's for 100 people). Without trying to appear as if I'm defending gitlab itself, I've always been of the notion of "Do it right and then do it fast". This is how postgresql is starting to beat the ever-loving crap out of mysql now, it used to be the slow option, now it's the one that wont eat your baby.
  - sytse 11y ago
    Thanks, we indeed recommend 2GB for all installations https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/install/requirements.md#memory https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/inst... I've made it a bit more clear in https://gitlab.com/gitlab-org/gitlab-ce/commit/b31c68aa2afbbcdb5459f156472fa44261de0a9c https://gitlab.com/gitlab-org/gitlab-ce/commit/b31c68aa2afbb...
amist 11y ago
Still waiting for issues priority levels. Without it, the issues page is just a mess.
- jobvandervoort 11y ago
  Thanks, I created an issue to discuss this. Would love to get your input. https://gitlab.com/gitlab-org/gitlab-ce/issues/13673 https://gitlab.com/gitlab-org/gitlab-ce/issues/13673
dudul 11y ago
Nice, looking forward to the upgrade to GitLab pages on gitlab.com !
- jobvandervoort 11y ago
  Thanks! Should be soon!
  - tdkl 11y ago
    Will there be a possibility to use an apex domain ? Looking to switch from GH Pages.
    - sytse 11y ago
      I'm not sure and asked Kamil to look into this.
    - ayufan 11y ago
      Yes. Sure. Instead of adding the CNAME you need to add an A record. You can get the IP address with dig: $ dig a myuser.gitlab.io Then configure your domain to point to that IP address. We are currently working on documentation covering that part too.
      - tdkl 11y ago
        Brilliant, thank you (and sytse below) for a prompt response. Looking forward to set it up.
quadrangle 11y ago
This comment is not meant to be the main judgment on what is otherwise an interesting update, but: > To focus on your content shows a screenshot with extremely long text lines that are far harder to read than than when the sidebar thing helps keep the lines to a still-too-long-but-not-as-bad length. How does nobody at GitLab realize that you need some max-width or a container or something to keep text line length comfortably readable‽ (the same can be said for Hacker News, but everyone seems to know that it's ugly already)
- Strom 11y ago
  I imagine the fact that not everybody cares about the length of lines is a factor. I keep hearing people complain about various wide articles, but I've never noticed any problems reading such content myself. Thus having some small max-width definitely isn't a universal requirement.
- Gigablah 11y ago
  Uh oh, here comes the "max-width = readability" cargo cult.
  - quadrangle 11y ago
    "cargo" cult??? Don't you just mean "cult"? How does this have anything to do with cargo cults even metaphorically?
    - alextgordon 11y ago
      The "cargo" is self-referential, clearly. It's a cargo cult "cargo cult".
- mikewhy 11y ago
  There's already a setting for that http://imgur.com/GftE0Wx http://imgur.com/GftE0Wx
  - quadrangle 11y ago
talles 11y ago
> yes, all important things for those of you that speak Spanish or Portuguese What do they mean by that?
- arturhoo 11y ago
  I'm Brazilian and needed a few seconds to understand what they meant. I kept reading it like to-do(s). In the end they're just playing with the word: https://translate.google.com/#pt/en/todos https://translate.google.com/#pt/en/todos
  - talles 11y ago
    Thank you for making me click. That's such a bad pun. (I'm Brazilian too)
    - jobvandervoort 11y ago
      I'm sorry, I thought it was hilarious. We wanted to acknowledge some people's frustrations with our chosen way of writing Todos.
- vinay427 11y ago
  >Not only have we increased performance for everyone, getting to what is important is now super quick with Todos todos means all/everything in Spanish and Portuguese.
- jdcarr 11y ago
  It's a Spanish/English pun. Todos means "all" in Spanish, so "all important things" But also Todos as in multiple Todo items.
praseodym 11y ago
Their performance graph shows response timings up to 25 seconds [1]. GitHub's mean web response time goes up to 200 milliseconds. The difference is two orders of magnitude. Is GitLab really that much slower?! [1] https://about.gitlab.com/images/8_5/issue_timings.png https://about.gitlab.com/images/8_5/issue_timings.png [2] https://status.github.com/ https://status.github.com/
- Keats 11y ago
  It is extremely slow. We tried it on a 1go droplet and it felt slow with 2 users but can't beat that £0 price.
  - sytse 11y ago
    Just so you know, we recommend a minimum of 2GB https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/install/requirements.md#memory https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/inst...
  - mrmondo 11y ago
    Have you tried running GitHub EE on something of the same spec? It's terrible to near impossible and it doesn't include nearly as many of the features as Gitlab. We have been running Gitlab for 100~ employees for well over a year on a single, medium/low specced VM and its lightning quick, so much so that when Devs/Ops have to use GitHub you can hear the sighs around the office!
    - sytse 11y ago
      Glad to hear GitLab is fast for you! Will be even faster with 8.5 :)
      - mrmondo 11y ago
        Seriously Sytse, Gitlab has not only continued to improve, it's done so at rockets pace while (and here's the hard part) at the same pace also improved quality and test coverage. Do you remember a year or so ago when I was whinging about some regressions after several upgrades? Well I'll tell you what - there hasn't been any that have impacted us in such a long time upgrades - even to a major version - do not worry me one bit and our Devs are always excited to see what's new. I'm not sure if you remember but we're a non-profit, charitable organisation and GitLab has really helped us immensely over the past year. A damn fine product from a damn fine team, supported by a damn fine community.
nrclark 11y ago
Was 8.5 able to address either of these? Large commits can't be viewed: https://gitlab.com/gitlab-org/gitlab-ce/issues/10785 https://gitlab.com/gitlab-org/gitlab-ce/issues/10785 Users created via LDAP login continue to count towards the user-count even if the LDAP account is deleted: https://gitlab.com/gitlab-org/gitlab-ce/issues/11844 https://gitlab.com/gitlab-org/gitlab-ce/issues/11844
- sytse 11y ago
  Thanks for asking. For the first issue work is being done but we need more time https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/2705 https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/2705 The second issue seems more like something that could become a feature request than a concrete proposal. Consider leaving a comment in the issue with your proposal.
- dblessing 11y ago
  In EE there is a nightly LDAP sync worker that will auto-block any LDAP users that are no longer in the directory. This should address the active user count issue for licensing.
cheald 11y ago
Very easy upgrade from 8.4.3 to 8.5 on Ubuntu using the omnibus packages. I did have to install bundler in my system Ruby (I have RVM on the system; the install scripts executed via apt-get apparently doesn't care), but that was the only hiccup.
- sytse 11y ago
  You should not have to install bundler on your system to upgrade to 8.5. If someone else encounters this please open an issue so we can diagnose the problem.
  - cheald 11y ago
    Here's my console buffer from the installation: https://gist.github.com/cheald/6002dbe275a379a5f85a https://gist.github.com/cheald/6002dbe275a379a5f85a tl;dr: apt-get install gitlab-ce failed with "bundler not found". rvm use system; gem install bundler, apt-get install gitlab-ce and it worked fine.
    - sytse 11y ago
      Thanks, we'll look into this.
    - balameb 11y ago
      Can you create a backup with sudo gitlab-rake gitlab:backup:create and send us your results to support@gitlab.com? Please mention its coming from this thread.
    - balameb 11y ago
      Just to be clear. All we need is the output from the console not the actual backup. What I see from the result your getting is the actual backup command failing. From my experience this might be do to how its executed through the upgrade process and we can have a closer look at what failed when running the create command.
      - 11y ago
oneeyedpigeon 11y ago
I'd love to try GitLab out, but the OSX installation instructions [1] are a bit of a put off. I'm not even sure if that's the right URL, but it's where google takes me. The instructions refer to a "runner"; I'm not really sure I understand what that is, and it's not explained anywhere. The "ci" makes me think this is something to do with continuous integration, so I'm really not sure if this is the right thing to be looking at. The instructions also say "(In the future there will be a brew package)"; this is sorely needed! [1] https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/blob/master/docs/install/osx.md https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/blob/ma...
- jgillich 11y ago
  GitLab itself doesn't run on OS X. To try it, you can simply sign up on gitlab.com, it runs the enterprise edition.
- jobvandervoort 11y ago
  I'm sorry this is confusing. We're working on a better, more clear website. You were looking at the CI Runner, which is a part of our Continuous Integration. Simply go to https://gitlab.com/ https://gitlab.com/ and click in the top right to sign up for a free account. You can use that instance or set your own up by following the instructions at the download page [0]. [0]: https://about.gitlab.com/downloads/ https://about.gitlab.com/downloads/
- orf 11y ago
  You're reading the docs for the continuous-integration runner :)
  - oneeyedpigeon 11y ago
    I did suspect as much, but it's the first result when I google "gitlab OSX" and it's titled "Install on OSX - GitLab".
    - joepvd 11y ago
      Whenever you feel lucky, don't assume you are... ;)
exstudent2 11y ago
Much faster! I notice it's rendering large source files instead of displaying them as binary now, so great! One issue: I'm getting a really weird animation/hover over effect on the Gitlab icon in the upper left corner. Is that meant to happen? Is there a way to disable this. Other than that, everyone should upgrade to this version.
- sytse 11y ago
  Glad to hear that the rendering got better for you. That animation is our loading indicator introduced in GitLab 8.4. There is no way to disable it. However, it seems to have a lot of fans https://twitter.com/jerbob92/status/692089402030460929 https://twitter.com/jerbob92/status/692089402030460929 I hope it is less weird now that you know what it is for.
  - exstudent2 11y ago
    Rendering is flawless now. I figured it was for loading, but I still don't like it (and it renders very strangely in Safari -- try mousing over it). I would really like the option to disable it. I'm sure others like it though, cool option to have.
    - jobvandervoort 11y ago
      We're bringing the option to customise the interface to CE. If you run your own instance, you can replace the logo to disable it.
      - exstudent2 11y ago
        Thanks, will do. Looking forward to the interface customization options.
        sytse 11y ago
        Great! Docs for the branded login page are at http://doc.gitlab.com/ee/customization/branded_login_page.html http://doc.gitlab.com/ee/customization/branded_login_page.ht... The merge into CE is happening in https://gitlab.com/gitlab-org/gitlab-ce/issues/11489 https://gitlab.com/gitlab-org/gitlab-ce/issues/11489 and hope it will be in one of the 8.5 patch releases.
josteink 11y ago
Looking at this thread here, Gitlab seems to be much more open about their development than Github, and has a real sense of community, yet Github (still) remains the popular option, despite their more community-hostile traditional board-meeting decision process. Is there a gradual shift in the FOSS community towards Gitlab (which in all honesty would make more sense), or am I just seeing the enthusiast in this thread?
- dudul 11y ago
  I can't tell if there is a real shift, I would say no. GitHub, in a lot of people, is synonymous to Git. GitLab is superior in a lot of ways, more feature, open source, very open as you pointed out. Their pricing model supports free private repos. Not sure what it would take to really make people reconsider GitHub as the default goto place to host OSS repos.
  - x1024 11y ago
    "GitHub failing hard". GitLab is great, but it's kind of a copycat project. Nothing wrong with that, it's just there really isn't a compelling reason to join beyond "less-predatory pricing". And the people who care about that use private repos, not OSS.
    - dudul 11y ago
      For example, a lot of people complain about issues on GitHub. GitLab handles those much better, that could be a compelling reason to move, but somehow it doesn't seem to be enough. Private repo can be useful for early stage of OSS projects. Agreed though that it still feels too much like a clone of GitHub. The UI for example is way to close to the original.
      - stormbrew 11y ago
        Having used both there's more than enough in either that's bad to justify a switch to the other if you really want to. I personally prefer github's warts to gitlab's. In particular, I find that general site navigation on gitlab is quite tedious and it rarely centres useful information first. But that is very much a qualitative and not a quantitative complaint. The main thing I find extra useful on gitlab is the ability to mark a MR as a WIP.
dman 11y ago
Can i use dnf update on fedora to update the gitlab package if I have the repo installed? I am on fedora 23 and doing dnf update doesnt upgrade gitlab. Also doing a dnf install gitlab-ce gives me a message that gitlab-ce-8.2.0-ce.0.e17.x86_64 is already installed.
- sytse 11y ago
  It worked with rpm so I assume dnf should work as well. Maybe you have to update your sources first since we have our own package server? If maybe you installed the package by downloading instead of adding the source server? Consider following the instructions on https://about.gitlab.com/downloads/ https://about.gitlab.com/downloads/ (the main instructions, not 'select and download the package manually and install')
lgp171188 11y ago
Great job GitLab team! Way to go! Unfortunately I cannot use it for my projects till the issue https://gitlab.com/gitlab-org/gitlab-ce/issues/12920 https://gitlab.com/gitlab-org/gitlab-ce/issues/12920 exists. Hopefully, it will be resolved some time in the future. I am firm believer in FOSS and I am very glad with GitLab embracing it as much as possible without affecting their revenues. I have started creating my new repositories on GitLab from this month
- sytse 11y ago
  Thanks! I see I already commented on your request 20 days ago and I've left a new one just now. Cool that you have started creating your repo's on GitLab.
monksy 11y ago
Awesome that theres a release.. but just as I'm migrating from one server that it has it built from source to a new one that uses the omnibus package.
giancarlostoro 11y ago
Are there any blog posts about techniques used to improve performance you guys would care to share? Thanks!
- YorickPeterse 11y ago
  Not yet, but I've been thinking of doing so. The difficulty is that you basically have to write the blog post (or at least take a lot of notes) while solving problems as otherwise you'll end up forgetting all the intricate little details.
  - giancarlostoro 11y ago
    That's fine, I'm just curious because you usually learn a great deal. If anything the biggest performance changes could be nice, though it may mostly be small tid bits here and there (though large overall). Thanks for all you guys did!
    - YorickPeterse 11y ago
      I still have a bunch of notes laying around from the changes we made for 8.5 so I'll take a look at those. For future changes (except maybe small ones) I'll see if I can just write down 1 or 2 sentences what I did _after_ I did it, stringing together a blog post from that should be easier than doing it from scratch. I created an issue about this so I won't forget: https://gitlab.com/gitlab-com/www-gitlab-com/issues/568 https://gitlab.com/gitlab-com/www-gitlab-com/issues/568
      - sytse 11y ago
        Awesome!
      - giancarlostoro 11y ago
        Thank you very much, learning from others is an invaluable way of learning to improve code and write code with a improved approach. Also a great way to try and avoid bugs when your code reminds you of a reported bug. Thank you again! Will look forward to reading future detailed development blog posts, it wont have to be every single little detail, but those small things that make a difference are handy to read over. Thanks again!
koolba 11y ago
Maybe a stupid question but is there a publicly hosted GitLab that provides free repo space (and the usual pay for private repos) or is it only self hosted?
- nikolauska 11y ago
  https://gitlab.com/ https://gitlab.com/ with free public and private repositories
  - koolba 11y ago
    Ok I didn't see that. The rest of the copy on the (particularly the pricing page) seems to indicate it's only local.
    - sytse 11y ago
      There is no pricing information there because it is free with forum support. But I agree it is confusing and made https://gitlab.com/gitlab-com/www-gitlab-com/issues/567 https://gitlab.com/gitlab-com/www-gitlab-com/issues/567 to remedy that.
nikolay 11y ago
I love GitHub, I'm loyal and grateful to them for all they've done for us, but GitLab is significantly more agile these days and loyalty easily can be reassigned. Even Bitbucket is picking up development, so, if I was GitHub, I'd really seriously reorg and ramp up development and innovation!
mrmondo 11y ago
Another great release in an incredibly fast turn around time, well done to the team and everyone that's contributed.
joaoqalves 11y ago
When I met Gitlab, 3 years ago, I didn't expect this. The product is so much mature, the UI is so much better and the feature-set increased too. I respect these guys. The competition is though out there. Github is _the_ place where many git users started and is the _de facto_ standard for open-source/show-cases or even tech blogging, these days. There are a few things that annoy me as a Gitlab user (UX things), apart from the search/responsiveness of the application. Moreover, they improved _a lot_ the installation/upgrade process over these years. I'm expecting big things from you now :) Anyway I need to say that these guys have been working a lot and deserve much credit. Kudos for you, guys! One of the things that annoys me most is that the homepage of the repository, where you have the README is not the same where you have a file browser (Perhaps this is Github-biased, but is soooooo much better. Think about it :)
- echelon 11y ago
  The only thing preventing me from using Gitlab is that someone registered my username. I'm "echelon" on Github, Twitter, Gmail, and dozens of other services. I guess I missed the boat. :/
- sytse 11y ago
  Thanks! We think the displaying both project information and the files is too messy, but I can see you point. If you have any other UX suggestions feel free to share them.

603 points by doubleg 11y ago

We're super excited with GitLab 8.5. It's much faster, no matter the size of your instance (but especially for larger instances). The Todos, ability to revert commits and CNAME support for Pages, are things that have been much requested and we're happy to have now. As always, we're here if anyone has any questions about anything.

gpc 11y ago
https://gitlab.com/gitlab-org/gitlab-ce/issues/11489 https://gitlab.com/gitlab-org/gitlab-ce/issues/11489 Didn't make it in?
- jobvandervoort 11y ago
  It seems not, unfortunately, I'm sorry if you were waiting for it. I'll discuss if we can ship it in a patch [0], otherwise it'll land in a month in CE. [0]: https://gitlab.com/gitlab-org/gitlab-ce/issues/11489#note_3857097 https://gitlab.com/gitlab-org/gitlab-ce/issues/11489#note_38...
  - gpc 11y ago
    Thanks, Looking forward to it. otherwise, congrats on another release!
    - jobvandervoort 11y ago
      Thanks! Consensus seems to be we can ship it somewhere this week.
      - gpc 11y ago
        I've been keeping an eye on that issue thread throughout the morning and although it doesn't seem appropriate for me to make a comment over there just to say this, I wanted to communicate it somewhere: the gitlab team is really impressing me in terms of responsiveness and flexibility. I really hope to see you keep that culture as you continue to grow and succeed. It doesn't go unnoticed!
        sytse 11y ago
        Thanks, glad to hear that. We're doing everything we can to keep and improve upon that culture. Being remote first and having a public issue tracker certainly helps, less difference between a comment of a co-worker and of a user.
fsiefken 11y ago
Hi Job, does this mean it is also faster in low memory environments like 512M? ToDo integration is a great feature!
- sytse 11y ago
  No, unfortunately not. We recommend 2GB of memory to run GitLab https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/install/requirements.md#cpu https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/inst... If 512MB is a requirement for you please consider using Gogs. Glad you like the Todos feature!
  - tshannon 11y ago
    I just wanted to say how awesome it is that you mention Gogs, a competing platform. It shows that you're focused on your domain, not closed-mindly discounting every competitor, and are open about any shortcomings in Gitlab.
    - sdesol 11y ago
      It also makes sense from a business point of view. The three strong points that I've taken from business school are: 1) You can overtake an incumbent if you can offer twice the value at half the price. If you can produce a drill that works two times better than existing drills at half the price, you'll overtake the drill market. 2) You can't compete with "as good as". Winning here is more marketing than anything and this is where companies like Apple and Coco-Cola shine. You can't beat Coke with point one, since it is impossible to produce something that is better than Coke. You can measure the performance differences between drills, but you can't measure the psychological value of Coke and Apple 3) You can't compete by price, unless you are dealing with a commodity product, which brings me to my point for posting. Turning "Git hosting" into a commodity product is not a bad situation for GitLab and I honestly think this is where it's heading. In a year or two, we'll probably see less tangible/understood things become the main selling point. Such as intelligent code reviews, better code management metrics, defect predictions and so forth. Edit: Forgot to mention that point 3 is also where Atlassian deserves a lot of credit. They are leveraging point 3 and trying to parlay it into point 1.
eadz 11y ago
Pages are an EE feature, but one which is useful for open source projects. Would you accept a pull request for a community implementation of Pages? or would a fork be needed in this case? How do you see this sort of issue playing out?
- ywecur 11y ago
  This is a very good question and something I'm always concerned about when it comes to open core products.
- sytse 11y ago
  Good question, how we deal with that is detailed on https://about.gitlab.com/about/#stewardship https://about.gitlab.com/about/#stewardship Please let me know if you have any questions.
dogweather 11y ago
Have you deployed it to gitlab.com?
- sytse 11y ago
  Not yet, from the OP: "For GitLab.com users: We plan to enable custom domains on GitLab.com in the following week, so stay tuned!"
orless 11y ago
Can it be that GitLab pages are down? I'm getting 503 at the moment: * http://gitlab-examples.gitlab.io/pages-plain-html http://gitlab-examples.gitlab.io/pages-plain-html * http://gitlab-examples.gitlab.io/pages-jekyll http://gitlab-examples.gitlab.io/pages-jekyll * http://www.downforeveryoneorjustme.com/http://gitlab-examples.gitlab.io/pages-jekyll http://www.downforeveryoneorjustme.com/http://gitlab-example...
- sytse 11y ago
  Sorry about that. There was a brief interruption to GitLab pages while we fixed a vulnerability. It is back now https://twitter.com/gitlabstatus/status/701897151790653440 https://twitter.com/gitlabstatus/status/701897151790653440
hinkley 11y ago
Is this release going to make any significant difference on the hosted projects? The last time I asked about Gitlab.com in a thread people mentioned that it's not more popular due to performance issues.
- sytse 11y ago
  Yep, so that is what we solved in this release. Title of the OP: "GitLab's fastest release ever". For more details see the announcement and https://gitlab.com/gitlab-com/operations/issues/42 https://gitlab.com/gitlab-com/operations/issues/42

pilif 11y ago

Nitpick: > GitLab no longer loads large Git blobs (e.g. binary files) into memory when browsing a Git repository. This prevents timeouts and memory leaks. Nope. Not loading something doesn't prevent memory leaks. It might make existing leaks not as bad (because you're leaking less). Either you're not leaking at which point it doesn't matter how big the thing you load is, it will get freed once it's not used, or you're leaking at which point, yes, if you only load small things, you get to run for a longer time before you die, but you will still die eventually. Only loading smaller things doesn't plug leaks. Aside of that: This looks like a very impressive release. Congratulations!

jobvandervoort 11y ago
Thanks for the nitpick, always welcome. I'm asking the author of the change what the background is on this. Will update the post if I can be more accurate. Thanks! UPDATE: Technically we're not fixing the leak, but this fix is reducing the impact significantly.
Ensorceled 11y ago
Nitpick on the nitpick. If the Git blobs were the source of the memory leak then this would, in fact, fix the memory leaks. Pretty aggressive stance when you may, in fact, be wrong.
- pilif 11y ago
  > If the Git blobs were the source of the memory leak then this would, in fact, fix the memory leaks. no. Because they are still reading git blobs - just only for the smaller files. > GitLab no longer loads large Git blobs (e.g. binary files) into memory [emphasis mine] So if their handling of Git blobs is leaking memory, then not reading the bigger blobs just gives them more leeway before they crash.
  - Ensorceled 11y ago
    Again, you may still be wrong. Many systems have different strategies for large blobs vs. small blobs (I know it's many because I've written several myself) including chunking strategies, separate memory pools etc. I'm taking this stand because I've had the exact issue we are arguing about: my large file handler had a leak in the memory pool for large blobs. Basically it was shared memory space for multiple processes so large objects could be passed out of band instead of using IO.

fweespeech 11y ago

> With GitLab 8.5, we’re offering GitLab Geo as an Alpha to all our Enterprise Edition customers. Once GitLab Geo has left Alpha / Beta state, a special license will be required to use it. I'm not sure I like this trend. While I understand some features GitLab may feel its worth a "second license" fee, it sets a bad precedent. Similarly, I don't want to give you $390/year for a GitLab instance with 2-3 users which keeps me from paying for the stuff I use for sideprojects. Although, tbh, if you are going the secondary license route for various features it seems I'm better off looking into an alternative and just implementing them myself. I honestly was just using the post-receive hook, etc. for this sort of thing.

akerro 11y ago
afaik there will be possibility to get a license for n users instead n*10 packs.
- jobvandervoort 11y ago
  That's correct.
  - lars_francke 11y ago
    Thanks for that. Can you give us details on when this change will happen?
    - jobvandervoort 11y ago
      We're not sure yet when it will happen, but we'll make it clear when we do. Update: our aim is before Q1 ends.
      - lars_francke 11y ago
        Great, thanks for the update.
jobvandervoort 11y ago

flashm 11y ago

I've moved all my private repos to Gitlab based on the chat on here and other places recently RE Github, Gitlab, and other solutions. I'm very happy overall, the interface is great. It's a bit slower than github currently (the web interface) as I'm using the online version rather than self hosted, but apart from that it's really bloody good. I'll be recommending it to others going forward and using it for all new repos that I want hosted.

jobvandervoort 11y ago
Thanks, that's good to hear. We're working hard on making it faster, this release being a major milestone in that work. Last release, we started shipping a performance monitoring tool [0], to make it easier to see what exactly is slow. [0]: https://about.gitlab.com/2016/01/22/gitlab-8-4-released/ https://about.gitlab.com/2016/01/22/gitlab-8-4-released/
- flashm 11y ago
  Nice, I'll take a look.
- sytse 11y ago
  Yep, also see our 'Make GitLab.com fast again' issue https://gitlab.com/gitlab-com/operations/issues/42 https://gitlab.com/gitlab-com/operations/issues/42 for updates about performance.
NDizzle 11y ago
What procedures did you follow to move your private repos over? I have been using private, self hosted git for years now. Were you able to move things over and keep commit history? (since I guess that's the only feature I currently have.)
- jobvandervoort 11y ago
  If you move your repository by importing it (in GitLab UI, under new project) or just by clone + pushing it yourself, you will always retain your entire commit history.

d33 11y ago

Two releases ago, updating was a bit of a pain for me, so I guess I'll wait until Friday with this one. Anyway, the new features sound really good!

jobvandervoort 11y ago
What was painful exactly?
- eknkc 11y ago
  First upgrade for me (8.4 -> 8.5) On a pretty small instance (1.7g ram google cloud) + 1gb disk swap the omninbus update failed with out of memory. Added some more swap space and it finished fine. It's probably not powerful enough to run it though.. Just a heads up.
  - jobvandervoort 11y ago
    I'm sorry to hear that. We advise a minimum of 2gb of ram, so I'd expect it run successful for you. I created an issue on the omnibus issue tracker about the memory requirement for upgrades, here: https://gitlab.com/gitlab-org/omnibus-gitlab/issues/1135 https://gitlab.com/gitlab-org/omnibus-gitlab/issues/1135 I'm glad you managed to solve it, though.

whitenoice 11y ago

Impressive release! Is there a guide on migrating from install from source to using omnibus? We currently upgrade from source but would like to move to omnibus.

jobvandervoort 11y ago
Thanks! To upgrade from source to omnibus: https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc/update/README.md#upgrading-from-a-non-omnibus-installation-to-an-omnibus-installation https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc... To see all our update guides: https://about.gitlab.com/update/ https://about.gitlab.com/update/
iBotPeaches 11y ago
Warning as someone who just did that. MySQL is EE only on Omnibus. I switched from Source (MySQL) to Omnibus only to find that MySQL was EE only. So I had to go back to Source.
- sytse 11y ago
  You are correct, we only ship our Omnibus packages with PostgreSQL. And the ability to use an external MySQL server is only in the Enterprise Edition. Switching away from MySQL might not be an option for you but documentation on how to convert from MySQL to PostgreSQL can be found on https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc/update/README.md#upgrading-from-non-omnibus-mysql-to-an-omnibus-installation-version-68 https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc...
- grokys 11y ago
  We recently switched from a source package using MySQL to the omnibus package and the migration to Postgresql was really easy and went without a hitch.
  - sytse 11y ago
    Glad to hear that, we try to keep the conversion instructions up to date and have tested them extensively.

palidanx 11y ago

I just upgraded and the diffs are WAY faster now. Thanks so much for all of the hard work!

jobvandervoort 11y ago
That's great to hear. It's a big community that makes this happen.
- palidanx 11y ago
  Just curious, were there any new changes made to branch creation and protected branches? I'm getting a Branch creation was rejected by Git hook When trying to create branches via my gitlab instance and it seems to take a lot longer to process the request. Pushing via a command shell seems to work well. --update I just rolled back my version to the older version and see that all of the branch functionality via the gitlab site works okay.
  - sytse 11y ago
    I'm not aware of any changes that would explain that error, but that doesn't mean it can't be a regression in 8.5. If so please open an issue for it and link from https://gitlab.com/gitlab-org/gitlab-ce/issues/13350 https://gitlab.com/gitlab-org/gitlab-ce/issues/13350

branchly2 11y ago

When I go to github, there's a search bar at the top to search for the public repo I'm looking for. I can't find the search feature at gitlab.com. How do I search for users or public repos of interest at gitlab?

jobvandervoort 11y ago
Use explore to search for interesting projects (and the people that have them in their namespace): https://gitlab.com/explore https://gitlab.com/explore Press `s` to search for anything. However we only support search for people in places where you immediately need them, like when adding to a project. I created a feature proposal to also search through people: https://gitlab.com/gitlab-org/gitlab-ce/issues/13672 https://gitlab.com/gitlab-org/gitlab-ce/issues/13672
- branchly2 11y ago
  Ok. I followed the Explore link, but I cannot find the search field on that page. It seems to only allow me to browse by trending/most-stars/all. Hitting 's' key on my keyboard doesn't seem to change the page in any way. Am I missing the search field? (Note, this is using Firefox/Iceweasel 44.0.)
  - audessuscest 11y ago
    I think you must be logged in to see the complete UI (with search field)
    - haynes 11y ago
      Indeed. The search field is currently only displayed for users that have logged in.
      - sytse 11y ago
        Thanks, that doesn't make sense so I made an issue to remedy it https://gitlab.com/gitlab-org/gitlab-ce/issues/13676 https://gitlab.com/gitlab-org/gitlab-ce/issues/13676

ausjke 11y ago

Still using redmine + gitolite here but have been watching Gitlab for a while, in fact I tried it yesterday and it's still quite resource hungry and slow(using DO's default installation with 1GB memory). Redmine+Gitolite has nearly everything I need but Gitlab's code view interface is better. Redmine's backend seems running more efficiently but its interface is not modern enough at this point, especially on how to review git repos.

dijit 11y ago
gitlabs minimum requirements are 2G of ram (although that's for 100 people). Without trying to appear as if I'm defending gitlab itself, I've always been of the notion of "Do it right and then do it fast". This is how postgresql is starting to beat the ever-loving crap out of mysql now, it used to be the slow option, now it's the one that wont eat your baby.
- sytse 11y ago
  Thanks, we indeed recommend 2GB for all installations https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/install/requirements.md#memory https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/inst... I've made it a bit more clear in https://gitlab.com/gitlab-org/gitlab-ce/commit/b31c68aa2afbbcdb5459f156472fa44261de0a9c https://gitlab.com/gitlab-org/gitlab-ce/commit/b31c68aa2afbb...

amist 11y ago

Still waiting for issues priority levels. Without it, the issues page is just a mess.

jobvandervoort 11y ago
Thanks, I created an issue to discuss this. Would love to get your input. https://gitlab.com/gitlab-org/gitlab-ce/issues/13673 https://gitlab.com/gitlab-org/gitlab-ce/issues/13673

dudul 11y ago

Nice, looking forward to the upgrade to GitLab pages on gitlab.com !

jobvandervoort 11y ago
Thanks! Should be soon!
- tdkl 11y ago
  Will there be a possibility to use an apex domain ? Looking to switch from GH Pages.
  - sytse 11y ago
    I'm not sure and asked Kamil to look into this.
  - ayufan 11y ago
    Yes. Sure. Instead of adding the CNAME you need to add an A record. You can get the IP address with dig: $ dig a myuser.gitlab.io Then configure your domain to point to that IP address. We are currently working on documentation covering that part too.
    - tdkl 11y ago
      Brilliant, thank you (and sytse below) for a prompt response. Looking forward to set it up.

quadrangle 11y ago

This comment is not meant to be the main judgment on what is otherwise an interesting update, but: > To focus on your content shows a screenshot with extremely long text lines that are far harder to read than than when the sidebar thing helps keep the lines to a still-too-long-but-not-as-bad length. How does nobody at GitLab realize that you need some max-width or a container or something to keep text line length comfortably readable‽ (the same can be said for Hacker News, but everyone seems to know that it's ugly already)

Strom 11y ago
I imagine the fact that not everybody cares about the length of lines is a factor. I keep hearing people complain about various wide articles, but I've never noticed any problems reading such content myself. Thus having some small max-width definitely isn't a universal requirement.
Gigablah 11y ago
Uh oh, here comes the "max-width = readability" cargo cult.
- quadrangle 11y ago
  "cargo" cult??? Don't you just mean "cult"? How does this have anything to do with cargo cults even metaphorically?
  - alextgordon 11y ago
    The "cargo" is self-referential, clearly. It's a cargo cult "cargo cult".
mikewhy 11y ago
There's already a setting for that http://imgur.com/GftE0Wx http://imgur.com/GftE0Wx
- quadrangle 11y ago

talles 11y ago

> yes, all important things for those of you that speak Spanish or Portuguese What do they mean by that?

arturhoo 11y ago
I'm Brazilian and needed a few seconds to understand what they meant. I kept reading it like to-do(s). In the end they're just playing with the word: https://translate.google.com/#pt/en/todos https://translate.google.com/#pt/en/todos
- talles 11y ago
  Thank you for making me click. That's such a bad pun. (I'm Brazilian too)
  - jobvandervoort 11y ago
    I'm sorry, I thought it was hilarious. We wanted to acknowledge some people's frustrations with our chosen way of writing Todos.
vinay427 11y ago
>Not only have we increased performance for everyone, getting to what is important is now super quick with Todos todos means all/everything in Spanish and Portuguese.
jdcarr 11y ago
It's a Spanish/English pun. Todos means "all" in Spanish, so "all important things" But also Todos as in multiple Todo items.

praseodym 11y ago

Their performance graph shows response timings up to 25 seconds [1]. GitHub's mean web response time goes up to 200 milliseconds. The difference is two orders of magnitude. Is GitLab really that much slower?! [1] https://about.gitlab.com/images/8_5/issue_timings.png https://about.gitlab.com/images/8_5/issue_timings.png [2] https://status.github.com/ https://status.github.com/

Keats 11y ago
It is extremely slow. We tried it on a 1go droplet and it felt slow with 2 users but can't beat that £0 price.
- sytse 11y ago
  Just so you know, we recommend a minimum of 2GB https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/install/requirements.md#memory https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/inst...
- mrmondo 11y ago
  Have you tried running GitHub EE on something of the same spec? It's terrible to near impossible and it doesn't include nearly as many of the features as Gitlab. We have been running Gitlab for 100~ employees for well over a year on a single, medium/low specced VM and its lightning quick, so much so that when Devs/Ops have to use GitHub you can hear the sighs around the office!
  - sytse 11y ago
    Glad to hear GitLab is fast for you! Will be even faster with 8.5 :)
    - mrmondo 11y ago
      Seriously Sytse, Gitlab has not only continued to improve, it's done so at rockets pace while (and here's the hard part) at the same pace also improved quality and test coverage. Do you remember a year or so ago when I was whinging about some regressions after several upgrades? Well I'll tell you what - there hasn't been any that have impacted us in such a long time upgrades - even to a major version - do not worry me one bit and our Devs are always excited to see what's new. I'm not sure if you remember but we're a non-profit, charitable organisation and GitLab has really helped us immensely over the past year. A damn fine product from a damn fine team, supported by a damn fine community.

nrclark 11y ago

Was 8.5 able to address either of these? Large commits can't be viewed: https://gitlab.com/gitlab-org/gitlab-ce/issues/10785 https://gitlab.com/gitlab-org/gitlab-ce/issues/10785 Users created via LDAP login continue to count towards the user-count even if the LDAP account is deleted: https://gitlab.com/gitlab-org/gitlab-ce/issues/11844 https://gitlab.com/gitlab-org/gitlab-ce/issues/11844

sytse 11y ago
Thanks for asking. For the first issue work is being done but we need more time https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/2705 https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/2705 The second issue seems more like something that could become a feature request than a concrete proposal. Consider leaving a comment in the issue with your proposal.
dblessing 11y ago
In EE there is a nightly LDAP sync worker that will auto-block any LDAP users that are no longer in the directory. This should address the active user count issue for licensing.

cheald 11y ago

Very easy upgrade from 8.4.3 to 8.5 on Ubuntu using the omnibus packages. I did have to install bundler in my system Ruby (I have RVM on the system; the install scripts executed via apt-get apparently doesn't care), but that was the only hiccup.

sytse 11y ago
You should not have to install bundler on your system to upgrade to 8.5. If someone else encounters this please open an issue so we can diagnose the problem.
- cheald 11y ago
  Here's my console buffer from the installation: https://gist.github.com/cheald/6002dbe275a379a5f85a https://gist.github.com/cheald/6002dbe275a379a5f85a tl;dr: apt-get install gitlab-ce failed with "bundler not found". rvm use system; gem install bundler, apt-get install gitlab-ce and it worked fine.
  - sytse 11y ago
    Thanks, we'll look into this.
  - balameb 11y ago
    Can you create a backup with sudo gitlab-rake gitlab:backup:create and send us your results to support@gitlab.com? Please mention its coming from this thread.
  - balameb 11y ago
    Just to be clear. All we need is the output from the console not the actual backup. What I see from the result your getting is the actual backup command failing. From my experience this might be do to how its executed through the upgrade process and we can have a closer look at what failed when running the create command.
    - 11y ago

oneeyedpigeon 11y ago

I'd love to try GitLab out, but the OSX installation instructions [1] are a bit of a put off. I'm not even sure if that's the right URL, but it's where google takes me. The instructions refer to a "runner"; I'm not really sure I understand what that is, and it's not explained anywhere. The "ci" makes me think this is something to do with continuous integration, so I'm really not sure if this is the right thing to be looking at. The instructions also say "(In the future there will be a brew package)"; this is sorely needed! [1] https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/blob/master/docs/install/osx.md https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/blob/ma...

jgillich 11y ago
GitLab itself doesn't run on OS X. To try it, you can simply sign up on gitlab.com, it runs the enterprise edition.
jobvandervoort 11y ago
I'm sorry this is confusing. We're working on a better, more clear website. You were looking at the CI Runner, which is a part of our Continuous Integration. Simply go to https://gitlab.com/ https://gitlab.com/ and click in the top right to sign up for a free account. You can use that instance or set your own up by following the instructions at the download page [0]. [0]: https://about.gitlab.com/downloads/ https://about.gitlab.com/downloads/
orf 11y ago
You're reading the docs for the continuous-integration runner :)
- oneeyedpigeon 11y ago
  I did suspect as much, but it's the first result when I google "gitlab OSX" and it's titled "Install on OSX - GitLab".
  - joepvd 11y ago
    Whenever you feel lucky, don't assume you are... ;)

exstudent2 11y ago

Much faster! I notice it's rendering large source files instead of displaying them as binary now, so great! One issue: I'm getting a really weird animation/hover over effect on the Gitlab icon in the upper left corner. Is that meant to happen? Is there a way to disable this. Other than that, everyone should upgrade to this version.

sytse 11y ago
Glad to hear that the rendering got better for you. That animation is our loading indicator introduced in GitLab 8.4. There is no way to disable it. However, it seems to have a lot of fans https://twitter.com/jerbob92/status/692089402030460929 https://twitter.com/jerbob92/status/692089402030460929 I hope it is less weird now that you know what it is for.
- exstudent2 11y ago
  Rendering is flawless now. I figured it was for loading, but I still don't like it (and it renders very strangely in Safari -- try mousing over it). I would really like the option to disable it. I'm sure others like it though, cool option to have.
  - jobvandervoort 11y ago
    We're bringing the option to customise the interface to CE. If you run your own instance, you can replace the logo to disable it.
    - exstudent2 11y ago
      Thanks, will do. Looking forward to the interface customization options.
      - sytse 11y ago
        Great! Docs for the branded login page are at http://doc.gitlab.com/ee/customization/branded_login_page.html http://doc.gitlab.com/ee/customization/branded_login_page.ht... The merge into CE is happening in https://gitlab.com/gitlab-org/gitlab-ce/issues/11489 https://gitlab.com/gitlab-org/gitlab-ce/issues/11489 and hope it will be in one of the 8.5 patch releases.

josteink 11y ago

Looking at this thread here, Gitlab seems to be much more open about their development than Github, and has a real sense of community, yet Github (still) remains the popular option, despite their more community-hostile traditional board-meeting decision process. Is there a gradual shift in the FOSS community towards Gitlab (which in all honesty would make more sense), or am I just seeing the enthusiast in this thread?

dudul 11y ago
I can't tell if there is a real shift, I would say no. GitHub, in a lot of people, is synonymous to Git. GitLab is superior in a lot of ways, more feature, open source, very open as you pointed out. Their pricing model supports free private repos. Not sure what it would take to really make people reconsider GitHub as the default goto place to host OSS repos.
- x1024 11y ago
  "GitHub failing hard". GitLab is great, but it's kind of a copycat project. Nothing wrong with that, it's just there really isn't a compelling reason to join beyond "less-predatory pricing". And the people who care about that use private repos, not OSS.
  - dudul 11y ago
    For example, a lot of people complain about issues on GitHub. GitLab handles those much better, that could be a compelling reason to move, but somehow it doesn't seem to be enough. Private repo can be useful for early stage of OSS projects. Agreed though that it still feels too much like a clone of GitHub. The UI for example is way to close to the original.
    - stormbrew 11y ago
      Having used both there's more than enough in either that's bad to justify a switch to the other if you really want to. I personally prefer github's warts to gitlab's. In particular, I find that general site navigation on gitlab is quite tedious and it rarely centres useful information first. But that is very much a qualitative and not a quantitative complaint. The main thing I find extra useful on gitlab is the ability to mark a MR as a WIP.

dman 11y ago

Can i use dnf update on fedora to update the gitlab package if I have the repo installed? I am on fedora 23 and doing dnf update doesnt upgrade gitlab. Also doing a dnf install gitlab-ce gives me a message that gitlab-ce-8.2.0-ce.0.e17.x86_64 is already installed.

sytse 11y ago
It worked with rpm so I assume dnf should work as well. Maybe you have to update your sources first since we have our own package server? If maybe you installed the package by downloading instead of adding the source server? Consider following the instructions on https://about.gitlab.com/downloads/ https://about.gitlab.com/downloads/ (the main instructions, not 'select and download the package manually and install')

lgp171188 11y ago

Great job GitLab team! Way to go! Unfortunately I cannot use it for my projects till the issue https://gitlab.com/gitlab-org/gitlab-ce/issues/12920 https://gitlab.com/gitlab-org/gitlab-ce/issues/12920 exists. Hopefully, it will be resolved some time in the future. I am firm believer in FOSS and I am very glad with GitLab embracing it as much as possible without affecting their revenues. I have started creating my new repositories on GitLab from this month

sytse 11y ago
Thanks! I see I already commented on your request 20 days ago and I've left a new one just now. Cool that you have started creating your repo's on GitLab.

monksy 11y ago

Awesome that theres a release.. but just as I'm migrating from one server that it has it built from source to a new one that uses the omnibus package.

giancarlostoro 11y ago

Are there any blog posts about techniques used to improve performance you guys would care to share? Thanks!

YorickPeterse 11y ago
Not yet, but I've been thinking of doing so. The difficulty is that you basically have to write the blog post (or at least take a lot of notes) while solving problems as otherwise you'll end up forgetting all the intricate little details.
- giancarlostoro 11y ago
  That's fine, I'm just curious because you usually learn a great deal. If anything the biggest performance changes could be nice, though it may mostly be small tid bits here and there (though large overall). Thanks for all you guys did!
  - YorickPeterse 11y ago
    I still have a bunch of notes laying around from the changes we made for 8.5 so I'll take a look at those. For future changes (except maybe small ones) I'll see if I can just write down 1 or 2 sentences what I did _after_ I did it, stringing together a blog post from that should be easier than doing it from scratch. I created an issue about this so I won't forget: https://gitlab.com/gitlab-com/www-gitlab-com/issues/568 https://gitlab.com/gitlab-com/www-gitlab-com/issues/568
    - sytse 11y ago
      Awesome!
    - giancarlostoro 11y ago
      Thank you very much, learning from others is an invaluable way of learning to improve code and write code with a improved approach. Also a great way to try and avoid bugs when your code reminds you of a reported bug. Thank you again! Will look forward to reading future detailed development blog posts, it wont have to be every single little detail, but those small things that make a difference are handy to read over. Thanks again!

koolba 11y ago

Maybe a stupid question but is there a publicly hosted GitLab that provides free repo space (and the usual pay for private repos) or is it only self hosted?

nikolauska 11y ago
https://gitlab.com/ https://gitlab.com/ with free public and private repositories
- koolba 11y ago
  Ok I didn't see that. The rest of the copy on the (particularly the pricing page) seems to indicate it's only local.
  - sytse 11y ago
    There is no pricing information there because it is free with forum support. But I agree it is confusing and made https://gitlab.com/gitlab-com/www-gitlab-com/issues/567 https://gitlab.com/gitlab-com/www-gitlab-com/issues/567 to remedy that.

nikolay 11y ago

I love GitHub, I'm loyal and grateful to them for all they've done for us, but GitLab is significantly more agile these days and loyalty easily can be reassigned. Even Bitbucket is picking up development, so, if I was GitHub, I'd really seriously reorg and ramp up development and innovation!

mrmondo 11y ago

Another great release in an incredibly fast turn around time, well done to the team and everyone that's contributed.

joaoqalves 11y ago

When I met Gitlab, 3 years ago, I didn't expect this. The product is so much mature, the UI is so much better and the feature-set increased too. I respect these guys. The competition is though out there. Github is _the_ place where many git users started and is the _de facto_ standard for open-source/show-cases or even tech blogging, these days. There are a few things that annoy me as a Gitlab user (UX things), apart from the search/responsiveness of the application. Moreover, they improved _a lot_ the installation/upgrade process over these years. I'm expecting big things from you now :) Anyway I need to say that these guys have been working a lot and deserve much credit. Kudos for you, guys! One of the things that annoys me most is that the homepage of the repository, where you have the README is not the same where you have a file browser (Perhaps this is Github-biased, but is soooooo much better. Think about it :)

echelon 11y ago
The only thing preventing me from using Gitlab is that someone registered my username. I'm "echelon" on Github, Twitter, Gmail, and dozens of other services. I guess I missed the boat. :/
sytse 11y ago
Thanks! We think the displaying both project information and the files is too messy, but I can see you point. If you have any other UX suggestions feel free to share them.