[go: up one dir, main page]

Skip to content

Add Merge Train support to AutoDevOps

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Problem to solve

Merge trains doesn't currently support Auto DevOps and it is causing a lot of confusion for our users.

Intended users

Further details

We are planning to inform users when their .gitlab-ci.yml file is not configured to use merge trains, when the setting for merge trains is enabled. For autoDevOps we should add the missing configuration for them.

Proposal

Following https://docs.gitlab.com/ee/ci/merge_request_pipelines/#configuring-pipelines-for-merge-requests

add only: [merge_requests] to the auto DevOps .gitlab-ci.yml file

the 1. Pipelines for merged results needs to be enabled in the settings

Permissions and Security

Documentation

Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Links / references

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.

Edited by 🤖 GitLab Bot 🤖