Skip to content

GitLab Next

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 43,023
    • Issues 43,023
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,340
    • Merge requests 1,340
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #121933
Closed
Open
Created Dec 25, 2019 by Orit Golowinski@ogolowinskiDeveloper

Add Merge Train support to AutoDevOps

Problem to solve

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

Intended users

  • Sasha (Software Developer)
  • Devon (DevOps Engineer)

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 Oct 27, 2021 by 🤖 GitLab Bot 🤖
Assignee
Assign to
Time tracking