Skip to content

Persist refspecs when create a pipeline

What does this MR do?

Currently, the system compose refspecs when runner fetches the job. This implementation leaves a significant race condition that refspecs could vary per the external dependencies state, such as merge request's WIP flag.

The system has to persist the refspecs when it creates a pipeline instead of composing refspecs dynamically.

What are the relevant issue numbers?

Related https://gitlab.com/gitlab-org/gitlab-ee/issues/7380

Does this MR meet the acceptance criteria?

Edited by Shinya Maeda

Merge request reports