Verify Engineering Update - December 4th, 2020

On Thursday, December 10th, Grzegorz will be leading a session on Prometheus, Grafana, and Kibana in the next Verify Tech Discussions meeting. If you don’t have the calendar invite, please let me know and I will get you added.

The Testing group has moved to a Combined Team. Which means that all engineers in the Testing group (both Frontend and Backend) will report to Ricky Wiens, instead of having separate managers for Frontend and Backend as we do on other teams (handbook change here).

This week AWS launched Amazon Elastic Container Registry Public and GitLab Runner was selected as an initial launch partner!

The Pipeline Authoring group has made great progress on the Pipeline Editor and Pipeline Visualization and will be rolling out an MVC in 13.7.

The Testing group will be rolling out and update to the Test Summary Widget for gitlab-org projects very soon. This update will add a quick way of identifying flakey tests for a particular build.

The Continuous Integration group is beginning work on a highly requested feature to add fast-forward merge support to Merge Trains. It’s exciting to see these continued improvements and enhancements to Merge Trains!

The Pipeline Authoring and Continuous Integration groups have been seeing nice results from using feature flag rollout issues to document release plans. Here are some examples from Pipeline Authoring and Continuous Integration.

A new Working Group was started to focus on creating better alignment, tooling, and training around our internal usage of Feature Flags at GitLab. If you have any feedback for the group or would like to contribute in some way, please let me know.

Last week Elliot sent in a slightly concerning photo from his neighborhood, so the topic for this issue Island-hopping Canadian Grizzly Bears. Yikes… I think Colbert was right about bears 😆

Reminder, if you have anything to share from where you live, please send it my way.

Thanks again for reading, and don’t forget to add any feedback you have to this issue, or send it to me directly either on Slack, or to dfrey@gitlab.com.