GitLab CI/CD UX Milestone Kick-off, 22 May 2020

Previous Meeting

Next Meeting

⏯

youtube image

►

From YouTube: UX Kickoff 13.1 - Release:Progressive Delivery

Description

Release:Progressive Delivery Group | GitLab
https://about.gitlab.com/handbook/engineering/development/ci-cd/release/progressive-delivery/

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

PD 13.1 Planning Issue (#2) · Issues · GitLab.org / CI-CD / progressive_delivery · GitLab
https://gitlab.com/gitlab-org/ci-cd/progressive_delivery/-/issues/2

Show alerts in environment index page (#214634) · Issues · GitLab.org / GitLab · GitLab
https://gitlab.com/gitlab-org/gitlab/-/issues/214634

Offer in-product guidance for deploying to AWS (#207830) · Issues · GitLab.org / GitLab · GitLab
https://gitlab.com/gitlab-org/gitlab/-/issues/207830

Allow parent project's developers to create pipelines for merge requests for fork MRs (#217451) · Issues · GitLab.org / GitLab · GitLab
https://gitlab.com/gitlab-org/gitlab/-/issues/217451

Notifications for when pipelines are fixed (#24309) · Issues · GitLab.org / GitLab · GitLab
https://gitlab.com/gitlab-org/gitlab/-/issues/24309

A/B testing Problem Validation (#676) · Issues · GitLab.org / GitLab UX Research · GitLab
https://gitlab.com/gitlab-org/ux-research/-/issues/676

Progressive Delivery: Needs UX Review (&3357) · Epics · GitLab.org · GitLab
https://gitlab.com/groups/gitlab-org/-/epics/3357

Cancel deployment jobs when there is an alert on an environment (#216949) · Issues · GitLab.org / GitLab · GitLab
https://gitlab.com/gitlab-org/gitlab/-/issues/216949

Implement Blue/Green Switch on Deploy Boards (#218140) · Issues · GitLab.org / GitLab · GitLab
https://gitlab.com/gitlab-org/gitlab/-/issues/218140

Set deployment Traffic Weight via UI (#218139) · Issues · GitLab.org / GitLab · GitLab
https://gitlab.com/gitlab-org/gitlab/-/issues/218139

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

A

Hi everyone and welcome to the attention of one UX kickoff for a progressive delivery. Vessel delivery is part of the release stage and focuses on anything from continuous delivery to feature Flags, progressive delivery and so on. Let's take a look further. We go towards the categories page. You can see. It focuses on a few product categories. Review F's incremental rollout, contains delivery and feature flags under feature flags. You can see blue green deployments each Blake's itself a be testing, there's a host of different things.

A

We're looking at the UX kickoff focus on issues that you exist, working on for 13.1 and beyond. So let's look at the Flemming issue and see what's on right now for a top priorities, point of view we are looking into showing alerts right in within the context of the deploy board on the environment page.

A

This allows us to show the user what has gone wrong within their environment right from the environments page. If humanities is active, you will see extra information such as the instances and pods, and will be able to show that alert information right within content go on. We want to offer work items towards the user when they're at the point the AWS and help them a little bit along their way.

A

The idea is when they are configuring, a variable for AWS deployment, we're gonna, add additional information within that view to help them on their way as quick as possible.

A

Furthermore, we're gonna see if you can allow rich request for work by planners to create pipelines for merge quests on works. What this allows is, for example, currently within the given project.

A

If a community either creates a merge quest from their project to the main gibla project, it means not. The not. The same pipeline will be run because of security concerns and no for temple. A gritty web will be spun out with this. We can allow users that are part of the github project, the main project, for example, to spin up that same pipeline after they have checked that, and this will allow the user to create that same pipeline.

A

Allow for smoother acceptance of that work request looking on we're, currently not a fiying, the user of when a Python has gone wrong when it has erred when it has failed with the email application. However, after the developer has pushed fixes, we are not informing them when it has gone right. This issue looks into that. Lastly, one of the bigger efforts from a validation point of view is looking into a/b testing. We figured out that we haven't don't know enough yet about a/b testing, and this isn't telling to fix that.

A

A be testing is going to be a great focus of progress, delivery or the future plagues. A section of that and the more information we can gather and the more efficient will be at implementing it.

A

Lastly, we're going to have: we have an issue that focus on UX discussions or any issues that are beyond the next one or two releases. There's this issues, but focus on that we've got three issues to look into: it is about canceling deployment jobs when there's an alert on the environment. This kind of falls into write. One of the issues we discussed before, where we're showing ingress alerts on the deploy board, and we want to like if we cancel a deployment job because of such an alert.

A

We want to enable that.

A

Lastly, we want to allow use for Bluegreen switches, so if they want to switch between those environments right from Portland board, and the last issue is also to allow for ingress traffic waiting to be set through the UI in order to properly funnel that that internet traffic to the right environment in the right portions.

A

Lastly, the UX group is also focused on managing UX tab. This is wonderful performance indicators for us apartment, you're, actually doing a backlog, grooming and working together with product management in order to get UX that scheduled and fixed. This allows us to maintain and improve the application from a maintenance point of view and allow for existing features to be working even better.

A

Thank you so much. This was the u.s. key card for progressive delivery for 13.1. I'm your host me tree and checking out.