GitLab Pipeline Execution, 22 May 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: UX Kickoff 13.1 - Verify:Continuous Integration

Description

For all 13.1 Verify and Release kick-off videos:

13.1 Verify and Release UX Milestone Kick-off (#6) · Issues · GitLab.org / Verify and Release UX Team · GitLab
https://gitlab.com/gitlab-org/verify-and-release-ux-team/-/issues/6

Pages as shown in the video!

Verify:Continuous Integration Group | GitLab
https://about.gitlab.com/handbook/engineering/development/ci-cd/verify/continuous-integration/

Product sections, stages, groups, and categories | GitLab
https://about.gitlab.com/handbook/product/categories/#continuous-integration-group

13.1 Planning Issue (#3) · Issues · GitLab.org / CI-CD / continuous integration group · GitLab
https://gitlab.com/gitlab-org/ci-cd/continuous-integration/-/issues/3

Make pipeline permissions more controllable and flexible (#35067) · Issues · GitLab.org / GitLab · GitLab
https://gitlab.com/gitlab-org/gitlab/-/issues/35067

UI to browse locked artifacts (#217511) · Issues · GitLab.org / GitLab · GitLab
https://gitlab.com/gitlab-org/gitlab/-/issues/217511

CI linter should advise of errors/warnings/deprecations (#216444) · Issues · GitLab.org / GitLab · GitLab
https://gitlab.com/gitlab-org/gitlab/-/issues/216444

CI: Needs UX Review (&3374) · Epics · GitLab.org · GitLab
https://gitlab.com/groups/gitlab-org/-/epics/3374

Do not show `detached` label if it is not possible to run as `attached` (#217718) · Issues · GitLab.org / GitLab · GitLab
https://gitlab.com/gitlab-org/gitlab/-/issues/217718

UX Department Performance Indicators | GitLab
https://about.gitlab.com/handbook/engineering/ux/performance-indicators/#ux-debt

A

Hi, everyone welcome to the UX Cape output, 13.1 continuous integration, which is part of the verify stage. Continuous integration focuses on all functionality perspective the continuous integration stage, we're going to look at it from the wax point of view. So what will be for Tom by you acts or what we focus on for future releases?

A

We look at the continuous integration group. It is responsible for a few product categories under which continuous integration itself merge trains and the newly introduced Jenkins important. When we move to the 13.1 planning issue and scroll down towards the UI use experience section, you can see there's a few priorities. The first one is making pipeline permissions more controllable and flexible. This is looking into how to give pipelines more access, for example, to write to the repository itself from a security point of view, because currently they're quite limited. This is on purpose because of security concerns.

A

Next, there will be other priorities as well, such as the sea Islander. How can we advise the user sooner rather than later in terms of errors, warnings and applications towards their CI configuration, which will be limited? And lastly, there is the UI team browser lock artifacts, these artifacts are, they will not expire, and we want to give the user an easier way to navigate and get to know about which artifacts are a lot.

A

Lastly, there is the CI needs new acts with new issues. This is an issue that combines all the issues that we're going to focus on and drive conversation rather than immediately moving towards any designs are gonna, be implemented. The issue that we'll be focusing on right now is to not show the detached label if it is not possible to run the pipeline as an attached merchants pipeline.

A

So what this means is that, in an attached, merch quest pipeline scenario that the pipeline will run on the branch being merged hypothetically into the master branch or the default branch of whatever department branch is sometimes, this might not be possible. In that scenario, currently, we are still warning the user that the user is running an attached pipeline, even though that is not so informative.

A

A

From the US point of view, we are walking through the backlog for any UX tab and helping product management schedule back. It is one of the performance indicators for UX and allows us to get a good grasp on maintenance issues and tasks related to the gitlab user experience.

A

That was it. Thank you for joining me on this kickoff for UX and see you next time.