2 karma · joined July 23, 2018
If you don't mind can you please share the area you are located (roughly), I will bring this feedback to our infrastructure team.
We are currently working on upgrade testing for single-hop upgrades. We are hoping to have this for 11.9 going forward.
This effort is currently being tracked here https://gitlab.com/gitlab-com/www-gitlab-com/issues/4852
We are currently working on addressing performance, having a dedicated workstream for testing and measuring performance across the different GitLab versions.
Our plan is to publish the results across the versions as they have gone through testing. https://gitlab.com/gitlab-org/quality/performance/wikis/Benc...
We currently test for latency, I will take the average 500MS feedback to the team.
We have already identified slow endpoints with high latency so they can be improved. E.g:
* https://gitlab.com/gitlab-org/gitlab-ce/issues/66696 * https://gitlab.com/gitlab-org/gitlab-ce/issues/65323
Hi ori_b, do you have a link to an issue for this? Happy to bring this up to the team for prioritization.
In addition to using the bot to clean up stale issues, we are also using it for label hygiene and triage package automation.
- Label hygiene. Detect missed deliverable and track the version of regressions. See https://gitlab.com/gitlab-org/gitlab-ce/issues/49201 and https://gitlab.com/gitlab-org/gitlab-ce/issues/48518
- Triage package, we work remotely hence there is no bug grooming meeting, we do all of this in issues. A triage package is generated for each team by the bot every week. See https://gitlab.com/gitlab-org/gitlab-ce/issues/52781
You can set this up rather easily via the gitlab-triage project. The project is public https://gitlab.com/gitlab-org/gitlab-triage
You can see how the bot is being used in https://gitlab.com/gitlab-org/quality/triage-ops