Global Configuration for Gitlab Pipeline Config

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

  • Close this issue

Problem to solve

Allow for global configuration in gitlab-ci.yml

Intended users

  • Delaney (Development Team Lead)
  • Sasha (Software Developer)
  • Devon (DevOps Engineer)

Further details

Currently when doing an action for a pipeline job like specifying only: merge_requests you must do this for every job within the pipeline configuration for it to function as wanted. If you have a large pipeline this becomes cumbersome and repetitive. It would be amazing to have some general configuration you can provide within the yaml that will be applied for all jobs.

Documentation

Gitlab CI Pipeline Config docs should be updated to describe global configuration

Testing

With making gitlab-ci.yml more dynamic comes with it the risks of more ways to mess up the syntax within the yml. The required syntax for the yml to pass muster is fairly rigid right now and my proposal would make it more flexible

What is the type of buyer?

Core

Links / references

Edited Aug 19, 2025 by 🤖 GitLab Bot 🤖
Assignee Loading
Time tracking Loading