-
Notifications
You must be signed in to change notification settings - Fork 7
Open
Labels
A: CoreArea: core module, where plugins and builtin templates liesArea: core module, where plugins and builtin templates liesA: Plugin - StackArea: stack introspection and detection pluginsArea: stack introspection and detection pluginsS: DockerStack: DockerStack: DockerT: FeatureType: a new featureType: a new feature
Description
Context
According to the State of Developer Ecosystem 2021 survey by JetBrains, GitLab CI is the third most used CI system:
https://www.jetbrains.com/lp/devecosystem-2021/team-tools/#Which-Continuous-Integration-CI-systems-do-you-regularly-use
Following the Pipelinit roadmap to expand its supported platforms is necessary an implementation of all the current stacks on the GitLab platform.
Goal
Add Docker stack for GitLab platform
Implementation
GitLab organizes its CI on different way from GitHub, first it uses a central file called .gitlab-ci.yml and other CIs must be linked to him.
- Adapt the current GitHub implementation to the GitLab format:
Reference:
- https://docs.gitlab.com/ee/ci/jobs/
- https://docs.gitlab.com/ee/ci/yaml/
- https://docs.gitlab.com/ee/ci/yaml/#include
To test
- Create a free account on https://gitlab.com/
- Create a new repository and push a Docker project that you want to test Pipelinit
- Push a commit to a branch and then open a Pull request with changes following the stack you're working.
Obs: You can check if the pipeline is correct before a commit using the tool https://pypi.org/project/gitlab-lint/ , install it with python3 -m pip install -g gitlab_lint
Metadata
Metadata
Assignees
Labels
A: CoreArea: core module, where plugins and builtin templates liesArea: core module, where plugins and builtin templates liesA: Plugin - StackArea: stack introspection and detection pluginsArea: stack introspection and detection pluginsS: DockerStack: DockerStack: DockerT: FeatureType: a new featureType: a new feature