cmatija

We're really committed to improving the overall performance of GitLab.

You can take a look at some ongoing performance-related issues at https://gitlab.com/gitlab-org/gitlab-ce/issues?scope=all&utf... as well as some already completed improvements at https://gitlab.com/gitlab-org/gitlab-ce/issues?scope=all&utf...

There's also a plethora of ongoing efforts on making our hosted instance GitLab.com even faster. Lots of issues to look over at https://gitlab.com/gitlab-com/infrastructure/issues?scope=al...

Just wanted to add to this and point out that Gitter is already completely open-source and available at https://gitlab.com/gitlab-org/gitter/

Sorry about that. Could you provide more context about it? We'd love to help.

Are you already logged in when that happens to you? If so, you should open an issue in https://gitlab.com/gitlab-com/support-forum/issues with as much info as possible so we can look into it.

If you're getting that when you're trying to log-in, then you're having trouble accessing your GitLab.com account, with which our support team can help you - https://support.gitlab.com

That's our chart of backend sessions / sec for GitLab.com [1]. There's also a chart for frontend sessions [2], please keep in mind that there's a lot of CI / bot sessions on these dashboards. In addition to that there's much other interesting info on our HAProxy Grafana dashboard [3]. In case anyone's interested in even more metrics, there's a bunch of interesting dashboards on our Grafana instance [4].

[1] - http://monitor.gitlab.net/dashboard/db/haproxy-stats?refresh...

[2] - http://monitor.gitlab.net/dashboard/db/haproxy-stats?refresh...

[3] - http://monitor.gitlab.net/dashboard/db/haproxy-stats

[4] - http://monitor.gitlab.net/?orgId=1

Apart from what the community already outlined, we're always looking to improve performance of GitLab itself, you can check out our ongoing efforts in [1].

Apart from that, we'll also working on improving performance of GitLab.com. Here's a list of issues we're working on [2]

If performance is crucial to you, we invite you to try out a self-hosted CE instance. It should be fairly easy. We even have ready-made Docker containers [3]. As always, if there's any issues just ask away and we'll do our best to help.

[1] - https://gitlab.com/gitlab-org/gitlab-ce/issues?scope=all&utf...

[2] - https://gitlab.com/gitlab-com/infrastructure/issues?scope=al...

[3] - https://hub.docker.com/r/gitlab/gitlab-ce/

If you're referring to Related Issues, yeah. It's available only in Enterprise Edition Starter and Enterprise Edition premium.

If you're interested, you can take a look into how we determine which feature is EE - https://about.gitlab.com/stewardship/

Sorry to hear you're experiencing issues. Are you still affected? Are you logged in? If so, could you please open an issue in https://gitlab.com/gitlab-com/support-forum/issues with as much info as possible?

We have free private repositories for all users and you can organize users into groups. Is this what you're looking for? If not, could you provide more context into what you're looking for?

Sorry to hear you think our UI is awful. We're constantly trying to improve every part of the product, including our UX. There's a couple of ongoing initiatives currently, like the navigation overhaul [1]. You can list all current UX issues in [2]. We're also very appreciative of any and all community feedback. You can create an issue about anything specific you find bad in our UI (or any other part of the product) in [3].

We also like to think that we bring a couple of novel features to the game. You can check out a list of all our features in [4]

[1] - https://gitlab.com/gitlab-org/gitlab-ce/issues/32794

[2] - https://gitlab.com/gitlab-org/gitlab-ce/issues?scope=all&utf...

[3] - https://gitlab.com/gitlab-org/gitlab-ce/issues

[4] - https://about.gitlab.com/features/

Sorry to hear you think it's horrible.

We're working very hard on making it a pleasant and enjoyable experience. We're currently planning a navigation overhaul [1]. You can also check out a list of all current UX issues in [2]. And, any specific feedback is greatly appreciated, you can open an issue about anything at [3].

[1] - https://gitlab.com/gitlab-org/gitlab-ce/issues/32794

[2] - https://gitlab.com/gitlab-org/gitlab-ce/issues?scope=all&utf...

[3] - https://gitlab.com/gitlab-org/gitlab-ce/issues

We're working on lots of UX improvements. There's a navigation overhaul planned [1], you can also check out a list of all current UX issues with [2]. As always, community feedback is something we always welcome wholeheartedly [3]

[1] - https://gitlab.com/gitlab-org/gitlab-ce/issues/32794

[2] - https://gitlab.com/gitlab-org/gitlab-ce/issues?scope=all&utf...

[3] - https://gitlab.com/gitlab-org/gitlab-ce/issues

Sorry to hear you're displeased with our UI. We're always looking to improve our UI and UX as much as we can. There's currently a navigation overhaul planned [1]. If you have any other specific suggestions complaints about the UI we'd love to hear about it, you can even open an issue about it yourself [2]

[1] - https://gitlab.com/gitlab-org/gitlab-ce/issues/32794

[2] - https://gitlab.com/gitlab-org/gitlab-ce/issues

GitLab is envisioned as a platform for the full SDLC - from idea to production [1][2].

If you don't want to use the CI, it shouldn't get in your way. We'd love to hear any specific suggestions you might have, since we're always looking to improve. You can open an issue about them in [3] if you want.

[1] - https://about.gitlab.com/handbook/product/i2p-demo/

[2] - https://about.gitlab.com/direction/#scope

[3] - https://gitlab.com/gitlab-org/gitlab-ce/issues

Thanks for pointing this out.

I opened an issue about having a description of the project in the landing page: https://gitlab.com/gitlab-org/gitter/webapp/issues/1746

There's also https://gitlab.com/gitlab-org/gitlab-ce/issues/32794 which always shows you where you are (within GitLab), which is tangentially related

Hiya,

Sorry to hear you're displeased with our UI. We'd love to hear any suggestions you might have. We're always looking to improve as much as we can. You can open an issue in https://gitlab.com/gitlab-org/gitlab-ce/issues

Hiya,

Sorry to hear that you're displeased with our UI. We'd love to hear any specific feedback you might have. You can also open an issue in https://gitlab.com/gitlab-org/gitlab-ce/issues

We're always looking to improve

Hiya,

Anything specific about the UI you'd suggest changing? We'd love to hear your feedback so we can improve. Feel free to suggest improvements in https://gitlab.com/gitlab-org/gitlab-ce/issues

Here's the MR where that got implemented, so you can get a bit more context on it https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/10751

We have lots of ongoing UI work. You can always get an overview at https://gitlab.com/gitlab-org/gitlab-ce/issues?scope=all&utf...

If you have any specific issues, feel free to open an issue or share them here so I can open an issue for you.

Our Docker images source is stored in our omnibus repo [1]. We also have docs detailing the usage of our Docker images. [2]

[1] - https://gitlab.com/gitlab-org/omnibus-gitlab/tree/master/doc...

[2] - https://docs.gitlab.com/omnibus/docker/

Thanks for pointing this out. I opened a new issue about this; here https://gitlab.com/gitlab-org/gitlab-ce/issues/34246

We have a pretty detailed post-mortem on the timeline of events for the outage, as well as actions taken after it to prevent anything similar in the future (with links to related issues). You can check it out in https://about.gitlab.com/2017/02/10/postmortem-of-database-o...

Hiya,

Which features would you like to see in GitLab? We'd love to talk about it. You could also open a feature proposal issues in https://gitlab.com/gitlab-org/gitlab-ce/issues.

Which part of integrating with GitLab do you find difficult? We'd love to talk about it and improve.

Maybe we could open some issues and talk about what you'd like to have but is missing, or some things you think we're doing wrong.

* You could use our API to integrate with GitLab [1]

* You could develop a fullblown project service and contribute it to the codebase [2]

* You could use custom webhooks to add custom functionality [3]

[1] - https://docs.gitlab.com/ee/api/

[2] - https://docs.gitlab.com/ce/user/project/integrations/project...

[3] - https://docs.gitlab.com/ce/user/project/integrations/webhook...

* Issue visibility

You can currently see an overview of issues and MRs assigned to you (as well as your GitLab TODOs).

* Repo access

You can narrow repo access to a certain group (i.e. make it internal) see [1]

* Group-level issue boards

We have an open issue for cross-project (group-level) issue boards, see [2]

* Multiple repos per project

We discussed opting for a non-repo-centric approach to projects in [3] Check out the discussion in there, to see our reasoning for sticking with one repo per project.

* Non code projects

You can disable the repository in a project, so you can focus on just the issues, or you can have a repository with only graphics.

We use both internally. Our organization project doesn't have a repository [4], and our marketing repo has lots of design stuff [5]

[1] - https://docs.gitlab.com/ee/user/permissions.html

[2] - https://gitlab.com/gitlab-org/gitlab-ee/issues/928

[3] - https://gitlab.com/gitlab-org/gitlab-ee/issues/1295

[4] - https://gitlab.com/gitlab-com/organization/issues

[5] - https://gitlab.com/gitlab-com/marketing/tree/master/design

Hiya,

Thanks for sharing this feedback.

* Closing issues via push

Automatic issue closing (e.g. via push or MR) should work (I just tried it out on a test repo) - see the docs[1]. Did you use the correct keyword? Maybe something went awry, but it's definitely supported. Or did I misunderstand you and closing them via push works, but the issue is something related to the issue board instead? Could you share a bit more info? We'd love to get that sorted out if it's a bug or problem.

* Issue Board usability

We'd like to make the issue board as best as it can be. Which part of it was confusing to you? Maybe we can open an issue about it and ping the UX team?

* CI

Could you detail the experiences you had with our CI? Were you using GitLab.com or a self-hosted instance? And if you were using GitLab.com, were you using your own or our shared runners?

You can definitely cancel jobs, strange that you had problems with it.

What failed in your job?

* Stability & Performance

With each release we're adding stability and performance improvements, see [2]. And as always, our infra team works hard to improve the same on GitLab.com, see [3]

[1] - https://docs.gitlab.com/ee/user/project/issues/automatic_iss...

[2] - https://gitlab.com/gitlab-org/gitlab-ce/issues/?scope=all&ut...

[3] - https://gitlab.com/gitlab-com/infrastructure/issues?scope=al...

Sorry that you had a bad experience using GitLab.com. We’re working on improving stability and performance on GitLab.com. There's several ongoing efforts in improving stability and performance (Gitaly[1], Infrastructure issues[2], ...)

We always run the latest version of GitLab on GitLab.com and we’re working on making (almost) all our deploys downtime free (Issue: [3], MR: [4]). Of course, you can opt to self-host GitLab. It’s easy and quick to setup and requires very little maintenance via our omnibus package [5], and of course, we're here to help you if you get stuck along the way.

[1] - https://gitlab.com/gitlab-org/gitaly

[2] - https://gitlab.com/gitlab-com/infrastructure/issues/?scope=a...

[3] - https://gitlab.com/gitlab-org/gitlab-ce/issues/26130

[4] - https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/9976

[5] - https://about.gitlab.com/installation/

Sad to hear that.

If you have any specific complaints or issues. We'd love to hear about them so we can improve.

Hiya,

Thanks for leaving some feedback.

* Speed

GNOME is looking to self-host their own GitLab CE instance. We understand that GitLab.com might have some performance issues. This is specific to our hosted GitLab instance due to its scale. A self-hosted instance on a much smaller scale is much much faster.

Also, we're always looking to improve GitLab performance - check out issues labeled "performance" in the GitLab CE repo [1] as well as issues in the infrastructure repo which are about .com specifically [2]

* Commits visible on the main tab

A list of commits is just a click away in the MR view, in the "Commits" tab. Also commits that are added are also displayed in the main tab.

* Can see new stuff that happened

The main MR tab lists the actions that happened related to it in a chronological order, from first to last. You can always look at that and see any new MR changes

* Sidebar

The sidebar is expanded by default on larger screen sizes and collapsed on smaller ones to preserve screen real estate for the MR itself.

I opened an issue about the icons themselves, see [3]

* View rendered files in MR

We have renderers for all kinds of files. But in a MR, we diff the MD source files. If we rendered them, diffing them would be almost impossible.

I opened an issue about having toggle-able rendering in the changes tab in MRs. Feel free to chime in in [4]

* Review mode

Could you explain this in a bit more detail? Maybe we could open a feature proposal for this functionality.

Hopefully I addressed all your concerns, feel free to add anything or dive into any of the issues, or even contact me personally.

[1] - https://gitlab.com/gitlab-org/gitlab-ce/issues?scope=all&utf...

[2] - https://gitlab.com/gitlab-com/infrastructure/issues?scope=al...

[3] - https://gitlab.com/gitlab-org/gitlab-ce/issues/32413

[4] - https://gitlab.com/gitlab-org/gitlab-ce/issues/32414

Heya,

Just wanted to let you know that we introduced long pooling with GitLab Runner version 1.9.0 (~ three months ago).

Also you might want to take a gander at https://about.gitlab.com/2017/04/10/upcoming-runner-changes-... We're throttling older runners.