Menu

1 / 2

Move GitLab CI to the built-in pipeline: how to rewrite the YAML

DEV Community: gitlab·Wen Ping·about 3 hours ago
#8yFNqiYL
#devtogitlab#devto#dev#deploy#pipeline
Reading 0:00
15s threshold

This article explains how to turn .gitlab-ci.yml into an AngusGit pipeline with Import GitLab CI , and what to change before you save. After reading it, you can use the unmapped list and the notes to handle artifacts , rules , and when that did not convert, add the branch limit back, and keep deploy from running when nobody has clicked. You create any credentials yourself.

Pipelines are available on Team and Enterprise. Community has no CI/CD menu. If you have not written an AngusGit pipeline yet, read the YAML getting-started article linked at the end first. A job is one group of steps in a pipeline. A runner is the program on a build machine that picks up a job and runs the commands.

1. A .gitlab-ci.yml used for the conversion

The file below is only for showing the conversion. It is not a file from a live repository.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.