Verify Engineering Update - January 22nd, 2021

Elliot was recently a guest on the IBM Z DevOps Talks podcast where he chatted about running GitLab Runner on IBM Z mainframes. You can listen to to episode here.

The Pipeline Authoring group had a huge release in 13.8 shipping the Pipeline editor, CI lint tool in the pipeline editor page, CI/CD configuration validation in Pipeline Editor, and Visualization of pipeline configuration! Great work everyone!

The Testing group shipped repeat failed test counter in 13.8 which is a super handy feature that will allow you to see if a test that is failing in your MR has failed on the default branch in the last 14 days. This will lead into the team’s roadmap feature for flaky test detection.

The macOS shared runners are now dogfooding themselves! Meaning, the pipeline that builds the code for the macOS shared runners now includes a job that runs on the macOS shared runners. If you think about it for a minute… it’s still a little confusing 😂

The CI group shipped a highly requested feature to allow users to enable Keep Latest Artifact at the project level.

We now have some snazzy new Grafana dashboard for the Verify stage groups. Thanks to the Scalability team for getting these setup for us! The dashboards can be found at the links below:

Grzegorz has updated the docs with some more details on how to contribute to the dashboards, and added build logs metrics to the CI dashboard.

As part of an effort to improve code organization and attribution, Fabio created a new Rubocop rule to enforce namespaced classes. Thanks to Fabio for supporting this effort!

As many of us in the northern hemisphere are likely looking forward to spring arriving, it got me thinking about the US tradition of Groundhog Day. As it turns out, using animals to predict weather isn’t an uncommon thing. From what I’m reading here, it seems that eastern Europe is more inclined to let bears predict the weather, while western Europe seems to prefer hedgehogs.

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.