View profile

Verify Engineering Update - October 8th, 2020

Revue
 
 
October 8 · Issue #1 · View online
Verify Engineering Update
Hi everyone!
Welcome to the first issue of the Verify Engineering Update newsletter. The idea behind this email is to share some recent highlights from the Verify stage. The hope is that, in doing so folks will have a better idea of what’s happening on other teams, and provide new opportunities for learning and collaboration. Thanks for reading, and please feel free to add any feedback you have to this issue, or send it to me directly.
Team
Pipeline Authoring Team
We have a new team! The new Pipeline Authoring team was created with the mission to make it as easy as possible for new and advanced users to create CI pipelines in GitLab. You can find out more on the category direction page, and learn more about the team on the engineering handbook page.
New Team Members
The recent Monitor realignment brought some new folks to Verify. Welcome to the team Nadia, Dov, Jose, and Miguel! Here’s where you can find them:
Quality Team Updates
The Quality Engineering team recently completed a realignment in the Ops section. As a result Zeff Morgan has moved from the Testing group to the Runner group.
CI/CD Demos
The AMER/EMEA demos meeting was this week and we had some really great presentations - you can watch the recording here. Thanks to Fred, Jose, Georgi, Sarah, Nathan, and Etienne for presenting!
Also a reminder to sign up for the APAC edition on October 14th.
Product
macOS Shared Runners Beta
Over the last several weeks we’ve been adding customers to beta release for macOS shared runners. The rollout is going well and team has been getting great feedback. We’re now over 20 customers in the beta!
Cloud Native Build Logs
The rollout of Cloud Native Build Logs on GitLab.com has been progressing nicely, and is a great example of how to create and use metrics to build confidence and provide observability into the rollout process. If you are unfamiliar with this project, you can read more about it in the architectural blueprint, or follow along in #f_cloud_job_logs.
Inline Code Coverage Visualization
Inline Code Coverage is shaping up to be one of the most popular features in the Testing group. This is a really nice feature, and you can find out more in the docs. Max also gave a demo last month which you can watch here.
Disable Shared Runners by Group
Many of our customers leverage the ability to deploy their own runners while still using the SAAS version of GitLab. A highly requested feature (>150 upvotes) is the ability to disable shared runners at the group level. This ensures that all jobs are executed by the customer’s self hosted runners. The team has been working hard on this feature and it will be rolling out soon.
Dedicated Area for CI Authoring
One of the first things the Pipeline Authoring group is working on is creating a dedicated area for CI Authoring. This will create a space in the application for much of the new visual pipeline building capabilities to come.
Process
Follow Up Issues
The Testing group is trying out a new process to better track and understand issues that get added mid-milestone. The hypothesis is that these are mostly follow up issues to work already in the milestone, but this process will provide more supporting data.
Progressive Feature Rollout Improvements
As a result of some recent regressions (1, 2), we’re working to improve guidance around progressive feature rollouts and operational metrics. Please take a look a the issues linked below and contribute any input or feedback you might have.
Culture
One of the great parts about working at GitLab is being able to work with people all over the world and learn about their customs and cultures.
In this issue we will learn some Canadian Slang.
If you have any interesting customs in your country that you’d like to share, please send them my way and I will include them in future updates.
Thanks
Thanks again for reading, and don’t forget to add any feedback you have to this issue, or send it to me directly.
Did you enjoy this issue?
In order to unsubscribe, click here.
If you were forwarded this newsletter and you like it, you can subscribe here.
Powered by Revue