Difference between revisions of "GitLab CI/CD"
Jump to navigation
Jump to search
↑ https://about.gitlab.com/releases/2020/01/22/gitlab-12-7-released/#parent-child-pipelines
↑ https://about.gitlab.com/releases/2020/01/22/gitlab-12-7-released/#pipeline-resource-groups
| Line 16: | Line 16: | ||
* GitLab CI project definition: Max artifacts size, protected and masked [[variables]], runners assignments | * GitLab CI project definition: Max artifacts size, protected and masked [[variables]], runners assignments | ||
* [[GitLab templates]] | * [[GitLab templates]] | ||
| − | * [[YAML: image:|image:]] | + | * <code>[[YAML: image:|image:]]</code> |
== See also == | == See also == | ||
Revision as of 19:17, 4 August 2022
GitLab CI/CD pipelines are configured using a YAML file called .gitlab-ci.yml.
News
- GitLab 12.7: Parent-Child Pipelines[1]
- GitLab 12.7: Pipeline Resource Groups[2]. To limit pipeline concurrency to force jobs to execute sequentially.
- GitLab 12.7: Delete a pipeline from the UI
- GitLab Ultimate 12.3: Security Dashboard
Related
- Gitlab runner
.gitlab-ci.yml- GitLab CI/CD variables
- GitLab CI project definition: Max artifacts size, protected and masked variables, runners assignments
- GitLab templates
image:
See also
gitlab-ci.yml,job: | stage: | stages: | artifacts: | include: | script: | when: | only: | needs:- GitLab CI, variables, templates, executors,
.gitlab-ci.yml, .gitlab/, Credential helpers, notifications, pipeline editor, Keyword reference, Changelog,ContainersNotReady, GitLab environments
Advertising:
