{"id":14580,"date":"2017-11-02T16:49:10","date_gmt":"2017-11-02T13:49:10","guid":{"rendered":"https:\/\/belvg.com\/blog\/?p=14580"},"modified":"2026-07-08T13:39:24","modified_gmt":"2026-07-08T11:39:24","slug":"what-is-git-pipelines-and-how-to-use-it-with-bitbucket-and-gitlab","status":"publish","type":"post","link":"https:\/\/belvg.com\/blog\/what-is-git-pipelines-and-how-to-use-it-with-bitbucket-and-gitlab.html","title":{"rendered":"What is Git Pipeline and How to Use it With Bitbucket and Gitlab In 2026"},"content":{"rendered":"\n

Git Pipeline provides an extensible set of tools for modeling build, testing, and deploying code. All jobs in a stage are executed simultaneously, and if it succeeds, the pipeline moves on to the next stage. If one of the jobs fails, the next stage is usually not executed.<\/p>\n

<\/p>\n

Stages<\/h2>\n

The following pipeline job steps in Magento 2.2 projects:<\/p>\n

1. Build <\/strong>– compilation and packaging of the project.
\n2. Testing <\/strong>– automated testing with default data.
\n3. Staging <\/strong>– manual testing and decision on going live.
\n4. Production <\/strong>– manual.<\/p>\n

\"pipelines\"<\/a><\/p>\n

Modern Magento projects usually use CI\/CD pipelines with Docker-based environments and supported PHP versions. The pipeline configuration should include dependency installation, automated tests, static content deployment, and build artifacts. Environment variables and secret management should be used for database credentials, API keys, and deployment settings. Before deploying to production, teams commonly add approval steps and automated checks to reduce deployment risks.<\/p>\n

How is it used with Bitbucket and GitLab?<\/h2>\n

Typically, the definition of a Git Pipeline is written into a text file, which is checked into a project’s source control repository.<\/p>\n

Bitbucket:<\/strong>
\nbitbucket-pipelines.yml
\nGitLab:<\/strong>
\n.gitlab-ci.yml<\/p>\n

Bitbucket features<\/h2>\n

– Custom params
\n– SSH Keys
\n– Integration with third-party services
\n– Free instances (4GB of RAM; 2 hours execution time; 5GB of disk space)<\/p>\n

Bitbucket Pipeline Structure<\/h2>\n

In order to describe the pipeline, we use yml.<\/p>\n

\"What<\/a><\/p>\n

Bitbucket example<\/h2>\n

bitbucket-pipelines.yml<\/p>\n

image: php:7.1.1\r\npipelines:\r\n  default:\r\n    - step:\r\n       script:\r\n          - apt-get update && apt-get install -y unzip\r\n          - curl -sS https:\/\/getcomposer.org\/installer | php -- --install-dir=\/usr\/local\/bin --filename=composer\r\n          - composer require magento\/product-community-edition 2.1.9 --no-update\r\n          - composer update\r\n          - rm -rf var\/di var\/generation\r\n          - php bin\/magento setup:install ...\r\n          - php bin\/magento cache:flush\r\n          - php bin\/magento setup:upgrade\r\n          - php bin\/magento setup:di:compile\r\n          - php bin\/magento indexer:reindex<\/pre>\n
Limitations of Bitbucket Pipelines<\/h2>\n
The free Bitbucket plan comes with a set number of builds and is available for only 50 minutes each month.<\/p>\n
Features that are not available for Pipelines yet:<\/strong>
\n1. Building Windows applications
\n2. Accessing services like artifact repositories or container registries behind a firewall<\/p>\n
<\/a>
\"magento
Magento Development Services<\/h3>
Take your online store to the next level with BelVG Magento development<\/p>Click to visit the page<\/span><\/a><\/div><\/div><\/div>\n
GitLab features<\/h2>\n
– Multi-platform
\n– Custom params
\n– SSH Keys
\n– Integration with third-party services
\n– Free instances
\n– Support local machine and private services
\n– Triggers<\/p>\n
GitLab Pipeline Structure<\/h2>\n
The GitLab structure of the pipeline is similar to the Bitbucket structure, with some minor differences:<\/p>\n
image: php:7.1.1\r\n\r\nservices:\r\n- solr\r\n\r\nvariables:\r\n- PORT: 8984\r\n\r\nbefore script:\r\n- configure solr\r\n\r\nafter script:\r\n- rm secrets\r\n\r\nstages:\r\n- build\r\n- deploy\r\n\r\njob1:\r\nstage: build\r\nscript:\r\n- executive-script-for-job1\r\nonly:\r\n- master<\/pre>\n
Limitations of GitLab Pipelines<\/h2>\n
You are limited to using only the CI predefined variables in the environment: name. If you try to reuse variables defined inside a script as part of the environment name, it will not work.<\/p>\n
If you need a full range of Magento development<\/a> services, turn to the BelVG company and get a professional consultation from ecommerce specialists.<\/p>\n\n","protected":false},"excerpt":{"rendered":"Git Pipeline provides an extensible set of tools for modeling build, testing and deploying code.","protected":false},"author":50,"featured_media":14594,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"image","meta":{"_acf_changed":false,"footnotes":""},"categories":[14,389],"tags":[],"class_list":["post-14580","post","type-post","status-publish","format-image","has-post-thumbnail","hentry","category-magento","category-magento2-development","post_format-post-format-image"],"acf":[],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t