Introduce Ci::BuildConfig model to move all YAML handling into this object (!21450) · Merge requests · GitLab.org / GitLab FOSS · GitLab

The 17.0 major release is coming on May 16, 2024! This version brings many exciting improvements to GitLab, but also removes some deprecated features. We are introducing three breaking change windows during which we expect breaking changes to be deployed to GitLab.com. You can read more about it on our blogpost . The first breaking change window begins 2024-04-22 09:00UTC and ends 2024-04-24 22:00UTC.

Kamil Trzciński requested to merge kamil-refactor-ci-builds-v2 into master Aug 31, 2018

What does this MR do?

My initial work on introducing Ci::BuildConfig model which should be used for presenting all CI-job-runner-oriented options.

Ideally, we should move everything that is crucial only for CI job processing to this class:

all variables,
all helpers generations and so on.

What are the relevant issue numbers?

Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/50195

Does this MR meet the acceptance criteria?

Changelog entry added, if necessary
Documentation created/updated
Tests added for this feature/bug
Conforms to the code review guidelines
Conforms to the merge request performance guidelines
Conforms to the style guides
Conforms to the database guides