merge_request_event For pipelines created when a merge request is created or updated. See Pipelines for external pull requests. external_pull_request_event When an external pull request on GitHub is created or updated. external When you use CI services other than GitLab. chat For pipelines created by using a GitLab ChatOps command. Common if clauses for rulesįor behavior similar to the only/ except keywords, you canĬheck the value of the $CI_PIPELINE_SOURCE variable: Value Description api For pipelines triggered by the pipelines API. To except: merge_requests, so job-with-no-rules Oneīranch pipeline runs a single job ( job-with-no-rules), and one merge request pipeline Job-with-no-rules : script : echo "This job runs in branch pipelines." job-with-rules : script : echo "This job runs in merge request pipelines." rules : - if : $CI_PIPELINE_SOURCE = "merge_request_event"įor every change pushed to the branch, duplicate pipelines run. Use needs to configure a job to run as soon as theĮarlier jobs it depends on finish running. To configure a job to be included or excluded from certain pipelines, use rules. You can configure jobs to run depending onįactors like the status of variables, or the pipeline type. When a new pipeline starts, GitLab checks the pipeline configuration to determine You are not allowed to download code from this project.Jobs or pipelines run unexpectedly when using changes:.Group variable expressions together with parentheses.Join variable expressions together with & or ||.Use predefined CI/CD variables to run jobs only in specific pipeline types.Fetch artifacts from a parallel:matrix job.Select different runner tags for each parallel matrix job.Run a one-dimensional matrix of parallel jobs. Combine multiple keywords with only or except.Use only:changes with merge request pipelines.only: variables / except: variables examples.Specify when jobs run with only and except.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |