The performance improvements are very noticeable : general page load times, pushing code to gitlab is as fast as github now and the commit messages load insanely fast, compared to a few months ago where loading commit messages in the UI used to take at least a couple of seconds. I don't follow gitlab development too closely, but they seem to have focused a lot on improving cache performance.<p>But one change that <i>I</i> did not like was the the removal of the side panel which could be pinned. Navigation required fewer steps, but now an extra click is required to bring up the options.
I love and use Gitlab and am excited about the 9.0 performance improvements.<p>On the other hand, I found it absurdly difficult to get feedback or action from Gitlab on an MR. There was an MR that fixed a critical problem in the virtualbox runner, and it sat there for about 5 months with no response to either the original submitter or my emails to gitlab/gitlab ci maintainers. About a month ago I finally decided to abuse your customer support addy to ask if somebody could force the maintainer to respond before the code rots. By that time the original submitter (who in comparison turned out to be easy to contact and collaborate with) was long gone. And another user had already announced a separate script they developed and maintained to work around the lack of merging this fix.<p>I'm glad it finally got merged, but it was only after deciding to use my free time and treat the process as a kind of game to be beaten. But that's a one-off game I won't play again. Plus I doubt the original submitter, a Go developer, will be making another merge request.<p>Anyhow, I made a list on the relevant issue tracker of the work it took to get the maintainer to eventually click the "merge" button:
<a href="https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/merge_requests/313" rel="nofollow">https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/merge_r...</a>
We've been using gitlab for most VideoLAN projects, and are moving towards it for all of them (including vlc and x264). A lot of things are great, and going in the right direction, but the issues tracker is really lacking.<p>The lack of custom fields, that you find in all other bugtrackers except github, and the lack of dependent issues are really blocking us to move full to gitlab.<p>And the biggest issue is that they're discussing to do it, but only in the non-open-source version, which we cannot use...
For anybody else wondering where that gorgeous cover photo is from: Queenstown, New Zealand :-)<p><a href="https://about.gitlab.com/images/9_0/9_0-cover-image.jpeg" rel="nofollow">https://about.gitlab.com/images/9_0/9_0-cover-image.jpeg</a><p><a href="https://www.google.ca/search?q=queenstown+new+zealand&source=lnms&tbm=isch" rel="nofollow">https://www.google.ca/search?q=queenstown+new+zealand&source...</a>
Congratulations on shipping 9.0. It's great to see a lot of improvements. Being able to reorder issues in the board is a welcome change. The subgroups is an interesting feature. I look forward to playing with it more.<p>I am still waiting on the ability to view issues on a board across a group (or now, a subgroup). Since Gitlab projects are repo-centric, I have hard time tracking issues across many repositories in a single place. A board that is visible at a group-level would solve this problem.<p>I believe this is a feature that's coming soon, though. I am looking forward to it.
Gitlab was really promising for my colleagues and I, but its inability to host git repos on the url root (aka gitrepo.mycompany.com/product.git) without hacking means its a no-go as we're not particularly inclined to redo all our development, deployment, and testing infrastructure. We use git a lot in our organization, including customer-facing stuff, so it would be a large transition.<p>Also stubborn coworkers who don't want to monkey with git settings.<p>Which is a shame, I really like gitlab and would love to replace gitolite :/
As much as I love GitLab the UI/UX is still very weak compared to GitHub. And the sidebar change is something in the completely wrong direction. You should also really check out how it looks on a 4k screen.
What convinced me to try out gitlab today: "Today with 9.0, we are excited to release Deploy Boards for environments running on Kubernetes. The Environments page of Pipelines now offers a single place to view the current health and deployment status of each environment, displaying the specific status of each pod in the deployment. Developers and other teammates can view the progress and status of a rollout, pod by pod, in the workflow they already use without any need to access Kubernetes."
Any documentation / talks / videos about the gitlab + kubernetes integration ? Thanks for the awesome product. At work we switched to gitlab for new projects and loving.
I like Gitlab, as an absolute noob I'm not really ready to make every mess of a program I use public (as Github requires). I fear that it can and will be used against me. I'm also such a small time user I think paying for Github is too much for my 3 > 200 lines projects. And so you end up at Gitlab. It works very well for me. If I want to, in the future, I can host it myself which is a nice thing. From this update I most like the dark-themed code view, yes I'm a simple man that is just learning how to code.
I would love to upgrade on my GitLab server, but I haven't been able to build GitLab with the omnibus builder since 8.14. I opened up a ticket but it hasn't garnered a response.<p><a href="https://gitlab.com/gitlab-org/gitlab-omnibus-builder/issues/7" rel="nofollow">https://gitlab.com/gitlab-org/gitlab-omnibus-builder/issues/...</a>
With the focus on performance, is there any chance we could get pagination on the deploy keys page? Our company is self hosting the CE version and we currently have 339 deployment keys. Every time we need to load the deployment keys page, it takes upwards of 20s. We could probably organize things differently and cut that down, but that would be a significant restructure and time investment for what would essentially be a band-aid. I (and others) have requested it before, but was told it was too low of a priority and it wouldn't be worked on.
I am having problem with de CI/CD after update:<p>```
Running with gitlab-ci-multi-runner 9.0.0[...]
Cloning repository...
Cloning into '/builds/xxxxxxx'...
warning: You appear to have cloned an empty repository.
Checking out xxxxxxx as master...
fatal: reference is not a tree: xxxxxx
```
The new enhancements seem very promising. We've been using gitlab for our internal use for a while now.<p>Having said that, every time a new gitlab release comes around, I always looks for updates in one area expectantly but mostly left unsatisfied. And that is, separation of the concept of Project from "one git repo"<p>E.g., I want to manage a project that ties in issues from various different git repositories. It's pretty common. Almost no actual "project" in a real life business is limited to just one git repo.<p>I want a system-wide wiki that collects knowledge about the entire operations. The idea that each wiki is tied to a particular git-repo is.. just... wrong.<p>Heck, even the new search feature across projects somehow doesn't include wiki's. How did that decision get made?<p>And so on and so forth.
Ah! Finally found the culprit :-)<p>I run my fleet of runners in pre-emptible instances on GCP (they die after 24h).<p>I forgot to pin the version in my startup script, so all it did was a simple apt-get install gitlab-ci-multi-runner.<p>For some reason, version 9 of the gitlab runner cannot connect to our Gitlab (it fires a 404 on register).<p>Anyways, look like 9 is a cool release, but we won't be upgrading until the sidebar comes back (did a little poll in the team and it 100% was in favour of the sidebar)
Awesome release!<p>What do people use to keep up to date with all the non-stop Gitlab releases? I used to use sandstorm but their port is very outdated by now (same goes for bitnami). I switched to cloudron and it has served me well but I am always on the look out for other solutions. On a side note, if you use the omnibus packages, are you a full time (or even part-time) sysadmin?
I wonder if this will provide a benefit in a resource constrained environment. I run the official Gitlab Docker/gitlab-ce container in a host with a J1900 processor and 4GB RAM and it is barely usable. Most pages timeout on the first load.<p>At present it looks like it hasn't been updated since 2015.
Any idea how I can upgrade my docker installation on Kubernetes? At the moment in my Helm chart i have specified exat Gitlab and Postgresql version. Do i need to bump postgresql too when changing Gitlab?
how is the CD in Gitlab complete without this issue being complete (<a href="https://gitlab.com/gitlab-org/gitlab-ce/issues/28497" rel="nofollow">https://gitlab.com/gitlab-org/gitlab-ce/issues/28497</a>) - is there any alternative if i want to use "gitlab.com" for hosting my code ?