GitLab 8.15 Released
11–20 of 117 posts
Re: GitLab 8.15 Released
#12Wow, that is an amazing release. Seems you actually managed to complete your goal right before christmas! This whole year has been quite impressive, I can't wait to see what you will do in 2017.
Re: GitLab 8.15 Released
#13Great stuff! One thing that's been broken for me for a while now: Raw links. I just get an empty response. It's kind of an important feature for me (and I'm sure others) so would love to see it fixed.
Re: GitLab 8.15 Released
#14Great stuff! One thing that's been broken for me for a while now: Raw links. I just get an empty response. It's kind of an important feature for me (and I'm sure others) so would love to see it fixed.
Re: GitLab 8.15 Released
#15Great stuff! One thing that's been broken for me for a while now: Raw links. I just get an empty response. It's kind of an important feature for me (and I'm sure others) so would love to see it fixed.
I don't understand what you mean by that. Can you create an issue about it [0] so we can discuss it and fix the problem (if applicable)? Thanks! [0]: https://gitlab.com/gitlab-org/gitlab-ce/issues
Re: GitLab 8.15 Released
#16I'd usually refrain from "+1" style comments, but you guys rock! Its great to finally see some improvements in the interface, but its still rather far from being as user-friendly as GitHub. I've got some very specific aspects in mind. Are contributions to Gitlab's interface accepted?
Can you share what these items are? I have used GitLab quite a bit and GitHub just a little, and I so far have enjoyed using GitLab much more. I had a hard time finding my way around on GitHub. The main parts I've used in both are creating Issues and Merge Requests, and in GitLab I've accepted them and managed teams/projects.
- On the main project page, the file list/table cells have too much padding. The same project's file list, with 22 files, on GitHub fits on my screen comfortably. On Gitlab, the whole table sits at 928px in height. Reducing the top/bottom padding in cells to 5px, without a loss in usability, yields a much nicer 708px height
- The two panels above the file list (the branch, and the latest commit) could be streamlined and merged
- Frankly, the whole area with the project name and the buttons below is incredibly and unnecessarily convoluted. Some important links are grayed, some others are not relevant for every project (e.g. I don't need a contribution guide for my private project)
- A lot of links are indistinguishable from text
Re: GitLab 8.15 Released
#17The 'quick fix' for setup these days is supposed to be to use a docker image... but the docker image most people use is unofficial, the maintainer is swamped and has a policy of ignoring problems, and although it runs it doesn't work well with real IPs/DNS/SSL/etc. for common cases (eg. email setup silently fails for many and has for ages - see https://github.com/sameersbn/docker-gitlab/issues/596 and https://github.com/sameersbn/docker-gitlab/issues/1005 which I recently opened) and adds the docker-is-a-moving-target complexity issue to the potential user's stack.
Normally I am based in China. Given that Github access is not super fast or stable there, you guys have a great opportunity to take that market. I'd personally love to use Gitlab both for my own business and those I consult for, but I can't get past go with mail on real infrastructure, and experiences with upgrades to date have been terrible.
Just offering my own recent experiences as a point of reference.
Re: GitLab 8.15 Released
#18@Gitlab: The features are great but the interface setup is shocking. That whole video assumes you have a K-cluster going already, and is a maze of this-thing, that-thing, auth-thing, copy-thing, etc. Have you guys ever tried interviewing users who are new or maintaining a Gitlab instance over major version upgrades? It's painful. The 'quick fix' for setup these days is supposed to be to use a docker image... but the…
Out of curiosity, why use the Docker image over our Omnibus package? Omnibus is generally what we recommend, but if that's not good enough we'd love to know how it can be improved.
Re: GitLab 8.15 Released
#19Holy hell this is amazing! Gitlab all the way! You release often and there is always something awesome in there, I love reading your release notes. One thing I find strangely lacking (seeing as you bundle it) is notifications from gitlab to mattermost when builds fail or issues/mrs are opened. Apparently I have to run some strange 3rd party application to process webhooks?
Build failures can be sent to Mattermost using our Pipeline webhooks described here: http://docs.gitlab.com/ce/web_hooks/web_hooks.html#pipeline-...
And then the Incoming Webhooks in Mattermost described here: https://docs.mattermost.com/developer/webhooks-incoming.html
Re: GitLab 8.15 Released
#20Earlier quoted context omitted.
I don't understand what you mean by that. Can you create an issue about it [0] so we can discuss it and fix the problem (if applicable)? Thanks! [0]: https://gitlab.com/gitlab-org/gitlab-ce/issues
When you're viewing a source code file, there are links to Raw, Blame, History, Permalink... The Raw link is broken (for me). I can create an issue.