GitLab’s free and paid offerings are all built around this Project feature. On GitLab you work with Projects, which correspond to software products (components, applications, etc.). Just like GitHub, GitLab is originally known for its source control and management system. Let’s first see how GitLab integrates CI/CD into their overall offering.
This time around, I’ll also take advantage of new deployment functionality in ActiveState’s CLI, the State Tool to reduce the execution time of our builds. If you read my post on setting up GitHub CI/CD, you’ll notice many similarities, mainly because both of these vendors come from an SCM background. In this post, I’ll explain how to set up a CI/CD pipeline on GitLab for a Python project, incorporating an ActiveState Python runtime environment and tooling, but the method applies equally to Perl projects, as well. But trailing GitHub in the marketplace, the company has been busy improving their game and creating products to cover all areas of Software Development Life Cycle (SDLC), with an aim to satisfying enterprise needs including CI/CD. As one of the leading Source Control Management (SCM) vendors, GitLab has a strong following in open source circles.
As part of my ongoing Continuous Integration/Continuous Delivery (CI/CD) series, it’s GitLab’s turn under the microscope.
0 kommentar(er)
