![]() ![]() ![]() This allows you to create local feature branches prefixed with “test/” and push them forward to verify how they will build in the CI environment. This pipeline is run whenever a branch named ‘test/*’ is pushed to the repository. The second definition, “test/*”, provides a pipeline definition that can be used for testing updates to the repository. That artifact is automatically deployed and integrated into the Dev instance on Acquia Cloud. At the end of execution, the deploy.sh script builds an artifact and deploys that to the Acquia Cloud repository. This pipeline is executed whenever a pull-request is merged into the develop branch. The first, “develop”, defines the pipeline configuration for updates to the develop branch of the repository. Under branches we have two pipelines defined. For our purposes we’ve created three pipelines definitions. Pipelines can be set to run on updates to branches, tags or pull-requests. The “pipelines” section of the configuration defines all of the pipelines configured to run for your repository. This was found to be necessary during the initial implementation. Having the clone depth set to full ensures we pull the entire history of the repository. We use the original Vagrant version of Drupal VM in Acquia BLT for local development. Here we’re using the Docker version of Drupal VM. This documents the image we’ll use to build the container. The top section of bitbucket-pipelines.yml outlines the basic configuration for the CI/CD environment. Bitbucket Pipelines uses Docker at its foundation, so each pipeline will be built up from a Docker image and then your defined scripts will be executed in order, in that container. ![]() bitbucket-pipelines.yml image: geerlingguy/drupal-vm:4.8.1 Let’s walk through an example of this configuration file built for one of our clients. This configuration file details how Bitbucket Pipelines will construct the CI/CD environment and what tasks it will perform given a state change in your repository. Configuration of Bitbucket Pipelines begins with the creation of a bitbucket-pipelines.yml file and adding that file to the root of your repository. Bitbucket Pipelines is a CI/CD service, built into Bitbucket and offers an easy solution for building and deploying to Acquia Cloud for project’s whose repositories live in Bitbucket and who opt out of using Acquia’s own Pipelines service. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |