GitLab GitLab Group Kickoffs - Verify:Pipeline Execution (formerly known as CI), 17 Mar 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: GitLab 13.11 Kickoff - Verify:Continuous Integration

Description

CI Planning for 13.11: https://gitlab.com/gitlab-org/ci-cd/continuous-integration/-/issues/49

A

Hi everyone, my name, is tal jaeger. I'm a product manager here at git lab for continuous integration. um Joining me is our product designer. Let her introduce herself.

B

Hi, I'm vittiga and I'm the product designer for verify. Ci.

A

um So we're here today to talk about what we have planned for the 13.11 milestone. What I'm sharing with you now is the category direction page for continuous integration.

A

You may recall last time, for when we did the kickoff for 13 uh 13.10. I talked about us tackling these particular bugs uh particular issues here. That is still our plan to continue work on that in 1311, and then there's also this other issue here, where we want to allow you to merge, even if pipeline must succeed, is enabled and there's an empty pipeline.

A

But what we want to go over today is the continued work that we're doing to focus on reducing our tech that and bug backlog, particularly we're, I'm going to talk through three bugs that we want to solve for you, so that it improves your experience using ci features and then vitica is going to finish off with three other uh bugs that we want to resolve in 13, 11., okay, so diving right into this one what's happening is when you delete a pipeline, not all the job artifacts are being deleted, and this is an important problem for us to solve, so that you have confidence that the the job artifacts will no longer remain.

A

That would add to the storage consumption overall, and then your costs associated with that.

A

That's there's the possible fix here is is um basically changing th having a new service that um deals with the uh moving the artifact records.

A

The next issue I want to talk about, which is another bug that is specific to a front-end resolution, is a misleading message that you get, that you can download artifacts when, in fact there are none. If you see here in this screenshot I'll zero in on it, there is this message to the right. This is the usual message that's displayed when there are artifacts to be downloaded.

A

Of course, we it's misleading to have it appear there when there are none, so we'll work to hide that when there are no artifacts to be downloaded and then a third bug that we want to solve for is not being able to run a pipeline via the ui when you have a custom ci path configured.

A

So this is a feature that we support that lets. You specify a ci yamo file for your ci config somewhere other than the root directory of your project, which is normally the default location, but in doing that, it's right now, if you haven't, if you haven't made any pipelines, no pipelines have run. It prevents you from going to click on the run pipeline and manually running it. What what's happening there is the logic that is looking for a user who has made any requests to be able to manually run a pipeline on that project.

A

It's it's being coupled together with displaying the run pipeline button. So we want to separate that out and make sure that run pipeline button is always visible. So you can manually run a pipeline.

A

um I'm going to turn it over to vitica to talk about the other, a few more bugs that we want to solve in 1311.

B

Thanks joe all right um so in this issue, um it talks about when we are on the pipeline page, the page where we are able to see a list of pipelines for a project so there, if you navigate to the mini pipeline graph, which is which is a part of the list and click on a state and then try to hover over the jobs which are part of the stage.

B

So it's not always that we see the tooltips uh appearing at the right place, and this is what this issue points at that the times when the tooltip it doesn't it kind of hides the job that it it should be over uh placed over or under so here for um the proposed solution.

B

um We are just saying that whatever we do right today, which is either placing the tooltip above or below the job uh should happen in all cases, and we should look at the edge cases where we are running into this bug that that's uh appearing.

B

So that's all for this one. Okay,.

B

All right so um tell if you can expand the left navigation of your yes, I think it would be easier. So on the left navigation, you see this ci cd option right, which is kind of uh right below merge, request and requirements there so just to make it appear and disappear. We have a toggle which is placed inside the settings general and then um under the visibility uh project, feature permissions and inside that section, which says visibility, project features permissions, there's a there's another section which is for repository where this toggle is placed.

B

So it's highlighted in this image uh and this toggle is under a headline. uh It has a heading that says pipelines and, of course I mean looking at this. It doesn't occur very naturally that this is something that would make the whole cicd option appear and disappear. So to make it more obvious, we are proposing a solution.

A

Sorry about that.

B

Here it is yeah yeah, so in this solution, what we are doing, first of all, we are taking this option out of the repository, so users don't feel that this is just another option.

B

uh I mean this is just another um sub option that they're going to see inside the repository navigation item on the left hand side, so we we're taking that out, and apart from that, we are also renaming it from pipelines to ci cd and changing the description a little bit to kind of communicate more clearly that which is the exact navigation item that this toggle controls.

A

Oh, I didn't even notice that that is going to be so much better. um Let me um let me look at that real quick and make it a little bigger, so I can compare the two so previously it was pipeline and it controlled whether or not ci cd appeared on the left now. Okay, thank you for that.

B

Welcome all right so coming to this last one. This is something very interesting which was uh pointed to us by one of our front-end engineers peyton. So he created created this issue, pointing that we have the ci lint button, which appears on the job page and since we do not have any evidence through all of the researches which have been conducted so far for ci to support that users really want this button to be here. We see we see absolutely no reason to uh keep it at the same location.

B

So this issue is to remove the c island button from the jobs page.

A

Yeah great, um that's it for the the six or so the half dozen bugs that I wanted to highlight for today there will be other issues that we work on in thirteen eleven.

A

I will add a link to our planning issue at the bottom of this video, where you can look at some of the other ones that we have planned, but these are our priorities for the milestone. Thanks for listening, everyone have a great day.