Uses the CI/CD configuration present in the fork project’s branch. Is created and runs in the parent (target) project, not the fork (source) project. Project members in the parent project can choose to run a pipeline for merge requestsįor a merge request submitted from a fork project. Pipelines for forks display with the fork badge in the parent project: Uses the fork project’s CI/CD configuration, resources, and project CI/CD variables. Is created and runs in the fork (source) project, not the parent (target) project. For example:Įxternal contributors who work in forks can’t create pipelines in the parent project.Ī merge request from a fork that is submitted to the parent project triggers a You can use the rules keyword to configure jobs to run in Your repository must be a GitLab repository, not an external repository. Source project to run a pipeline for merge requests. You must have at least the Developer role in the. 
Jobs that run in pipelines for merge requests.
Your project’s CI/CD configuration file must be configured with. Target branch with the changes in the earlier enqueued merge requests, to ensure The changes from each merge request are combined into the Merge trains, which run when merging multiple merge requestsĪt the same time. The result of combining the source branch’s changes with the target branch. Pipelines for merged results, which run on. Pipeline ran only on the contents of the source branch, ignoring the target branch. These pipelines display a detached label to indicate that the Pipelines for merge requests, which run on the changes in the merge request’s. The three types of pipelines for merge requests are: Do not have access to protected variables.īoth of these types of pipelines can appear on the Pipelines tab of a merge request. Have access to more predefined variables. The jobs in the CI/CD configuration file must be configured Is only available when pipelines for merge requests are configured for the pipeline. 
Select Run pipeline from the Pipelines tab in a merge request.Push a new commit to the source branch for a merge request.Have access to some predefined variables.Run when you push a new commit to a branch.This type of pipeline is called a pipeline for merge requests. This type of pipeline is called a branch pipeline.Īlternatively, you can configure your pipeline to run every time you make changes to the You can configure your pipeline to run every time you commit changes to a branch. The merge request’s pipeline is marked as failed but the latest pipeline succeeded Pipelines for merge requests.Two pipelines when pushing an invalid CI/CD configuration file.
0 kommentar(er)
