GitLab Gitlab 12.7 Release Kickoff, 17 Dec 2019

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: GitLab 12.7 Kickoff - Verify:Continuous Integration

Description

Allow skip ci on rebase via API
https://gitlab.com/gitlab-org/gitlab/issues/38141

(prelim work for...) Vault integration for key/value secrets MVC
https://gitlab.com/gitlab-org/gitlab/issues/28321

Trigger pipeline when another project is rebuilt
https://gitlab.com/gitlab-org/gitlab/issues/9045

A

Hello: everyone, my name, is Talia ger I'm, the product manager at net lab for verify. Continuous integration I'd like to highlight three issues that we will be working on in the 12.7 milestone. I'll share my screen and then we'll get started so first off allow skip CI on rebase via API and for this issue. What we'll be delivering is the ability to submit a rebase merge request without triggering CI.

A

This will be particularly helpful for those of you who have large mono repo, where there are many developers working in the same repository and where rebase is a common occurrence.

A

So if you, in those cases, don't want those rebase to result in the pipeline's running unnecessarily, this feature will allow you to pass a parameter to skip the CI on an mr for rebase. So that should be very helpful and we're excited to deliver it for the 12.7 milestone releasing on January 22nd next I want to mentioned for the vault integration MVC, which is currently scheduled for milestone 12.8.

A

We are starting some plan to work for that in 12.7, particularly work to validate possible solutions for the proposed feature, particularly a proof-of-concept for handling the credential secrets and tokens and rails, and this feature will allow you to access the secret stored in vault when using get lab CI platform.

A

That would mean for an automation, developer, who needs to access secrets as part of the build in the deploy process. They would have a way of fetching those tokens from vault and using it at runtime for a job on the CI CD pipeline. Again, although the actual feature itself is scheduled for milestone 1208, we were beginning work on valid the solution for that feature in 12.7 and finally, we have the issue to trigger pipelines when another project is rebuilt.

A

This is a carryover from a previous milestone that has been working progress. We are continuing this work with the plan to wrap it up for release on January 22nd, a quick recap. This is an Enterprise Edition feature that allows you to set a project to automatically trigger itself based on the successful builds on the master branch of another project, and that's it for what we're planning to work on or a release for 12.7 thanks for joining and have a great day.