GitLab 14.3 Release Kickoff, 17 Aug 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: GitLab 14.3 Kickoff - Pipeline Authoring:Verify

Description

No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).

A

Hi everyone- this is dr kobits, and this is the pipeline authoring kickoff video for 14.3. As always, we do have a planning issue in the public authoring group issue number 25.. This is going to be a light release and, in light of the business requirement that we have, we will prioritize our effort around sas reliability.

A

So most of our back-end effort will be dedicated toward improving the lower budget and we've already conducted the investigation regarding the error budget, and we found out that there are two endpoints that the most significant endpoint did contribute to that error budget.

A

One of them is the first issue here and the mirror pull api which would like to optimize and another one will actually get resolved in 14.4 as a part of the infra dev and work that is being done throughout this quarter.

A

Also because of the realignment and the addition of variables to pipeline authoring.

A

We want to conduct another second investigation about their own budget, because there were many other endpoints that were added to pipeline and also, um and also contribute to that lower budget. So in this investigation would like to make sure- and we found additional endpoint that contribute to that error budget and in the next iteration we'll work on optimizing that the idea is to reach the 99.95 percent.

A

Mark and with that, there is also several bugs and improvements and technical depths that we would like to work on.

A

One thing that I would like to mention is that this issue issue number five, is actually an issue that was in the previous iteration was a back-end effort, and this issue, by the way, is the foundation for the syntax highlighting and the auto-complete uh feature when someone is creating their pipeline configuration, but throughout the iteration we realized that this work is actually it makes more sense, the frontend team to lead- and this is why we've moved that to 40.3- and you can say this is marked as a fountain issue.

A

That's it as I mentioned a light iteration. We do have some filler issues in case we'll be able to complete all the deliverable and and as always, if you have any thoughts or questions, feel free to reach out or add your comments to this thread below. Thank you. Bye.