GitLab GitLab Group Kickoffs - Verify:Pipeline Execution (formerly known as CI), 18 Jul 2023

Previous Meeting

Next Meeting

⏯

youtube image

►

From YouTube: GitLab 16.3 Kick off - Verify:Pipeline Execution

Description

Add help text on job artifact to explain how to... (gitlab-org/gitlab#404657) and Highlight log line when hash is present in URL (gitlab-org/gitlab#406580) - improve connections between testing outputs, job logs, and artifacts to help people make decisions about their job failures
Pipeline Execution frontend instrumentation for... (gitlab-org/gitlab#409377) - Add data tracking to better understand usage patterns and inform the adoption journey of CICD at GitLab
Cannot obtain an exclusive lease for ci/pipelin... (gitlab-org/gitlab#331033) - Address a very confusing error that appears even though nothing has happened. This will be a great fix to minimize people's frustration using GitLab CI
Finally, continuing the prior milestone's work we will continue to support Fast Forward Merge with Merge Trains - hopefully getting to release it this milestone!

A

Welcome to the 16.3 kickoff, my name is Jackie Porter and I'm. The product manager over pipeline execution Group, which covers merge, strains, continuous integration and several other key categories for making CI level in 16.3. The team will be focusing mostly on Fast Forward, merge trains, rollout some usability fixes and some Data Tracking to help make us a little bit more efficient at making decisions based on product usage.

A

So, first up we have two issues that are qualified under usability they're, both related to improving how uh how there's connections between a job, artifact, a job log and helping people triage those failures. So this first one is adding some help. Checks to guide that experience and the second one is highlighting a log line when a hash is present in the URL. Both will improve and identify areas for people to better use testing outputs uh to uh to address their job failures.

A

Next up, we have some front-end instrumentation for Data Tracking, so we have this Ops section job to be done and there's several events that are on track today. uh So we don't really have visibility into what users are are using. So, for example, we found out that many people are actually taking advantage of accessibility, testing widgets, although the usage isn't reflected in that, so we need to have better granularity and understanding of usage so that we don't make decisions like deprecate, a feature based off of low usage.

A

Finally, we have some work related to a very annoying bug that gitlab is generating an error, but it doesn't need to generate an error because it's actually a non-error so to minimize people's frustration, we'll be addressing this error and closing it out. Another important thing in 16.3 is our rollout for feature flag. Our feature Flags uh for Fast Forward, word frames. This is again.

A

We really have been working on this for the past three milestones and we're hopefully going to get this in 16.3. Well, this is going to be the best release ever. If you have any questions, please reach out on any of the ethics issues and leave a comment for Jerry Porter.