nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Updating Drupal with Composer and pipeline

Richard Tremblay

Hi,

I have 10 websites built with Drupal 8 and each website has 2 environment (TEST & PROD), and each website has 1 repo in BitBucket, but the repo doesn't contain the Drupal files, only the custom theme (plus some external pages not related to Drupal).

When it's time to update Drupal core and all the modules, it requires a lot of time to connect to each environment and run Composer, so I was wondering if there's a better way to do it with pipeline (or anything else in BitBucket)?

Maybe I could add Composer.json in my repo and create a pipeline script that execute when I push into a specific branch (i.e. Composer-Test and Composer-Prod) and it will execute all the command directly in the server.

Any suggestions and how-to would be greatly appreciated.

Thanks.

Accepted answers

ktomk

This sounds like a build for deployment. Bitbucket supports three environments for deployment (test, staging and production) so this looks fitting for your TEST & PROD use-case.

The build does the composer install, so yes, at least somewhere you should place your `composer.json` file. IIRC Drupal 8 is compatible w/ Composer, go for it.

What does build and deployment mean here?

Instead of connecting to each environment you let Bitbucket create the packages (see artifacts) and in another step you can let do Bitbucket the deployments.

As you have a test environment I'd recommend to automatically deploy to test and make deploying to production a manual step so you can first review the test environments.

Keep in mind that for anything that you want to do w/ Bitbucket Cloud Pipelines Plugin, you normally need to have any file in the repository that is involved, e.g. composer.json.

If there is a reason why you did not considered to add it to the repository, this might be worth to review before continuing.

All comments

ktomk

This sounds like a build for deployment. Bitbucket supports three environments for deployment (test, staging and production) so this looks fitting for your TEST & PROD use-case.

The build does the composer install, so yes, at least somewhere you should place your `composer.json` file. IIRC Drupal 8 is compatible w/ Composer, go for it.

What does build and deployment mean here?

Instead of connecting to each environment you let Bitbucket create the packages (see artifacts) and in another step you can let do Bitbucket the deployments.

As you have a test environment I'd recommend to automatically deploy to test and make deploying to production a manual step so you can first review the test environments.

Keep in mind that for anything that you want to do w/ Bitbucket Cloud Pipelines Plugin, you normally need to have any file in the repository that is involved, e.g. composer.json.

If there is a reason why you did not considered to add it to the repository, this might be worth to review before continuing.

Richard Tremblay

Thanks for the information, looks like what I need.

Im no BitBucket expert, so I'm a little confused on how this will work tho.

From what I understand, I simply put the Composer.json in my repo, and I add a command in pipeline to execute Composer install/update, which will download all the Drupal 8 files inside BitBucket Cloud and after I can deploy them to my environments (Test first to review, and Prod after) ?

I don't want to ask too much, but if you could maybe break it down into steps that I need to accomplish, at least from there I can try to Google the details and do some test (I have setup a TEST Server with a BitBucket Repo where I can messed up anything and everything safely).

Thank you for your help

ktomk

Working step by step is a very good idea, no problems for asking.

A good start is PHP with Bitbucket Pipelines in the Bitbucket Support docs.

It shows how to choose the PHP image / version and how to install composer.

Then you do composer install. If that is already all you need then basically that pipeline step is done, give the step an artifacs enty:

- step:
image: php:7.4
script:
      - curl -sS https://getcomposer.org/installer | php -- --install-dir=/usr/local/bin --filename=composer
      - composer install
      - vendor/bin/phpunit --testsuite unit,integration
artifacts:
      - vendor

The next steps, e.g. deployments, don't need to do composer install any longer as the artifacts go over to the next step.

Try it out and feel free to ask any additional questions.

Richard Tremblay

I really appreciate your help.

If I understand correctly, Docker is a VM, and I can specify which configuration I want by providing a predefined image, which should be something that fits my needs to accomplish some automation and/or fit the server where I will deploy.

And in your example, pipeline download composer in the Docker, and run the install command.

At that step I get a message, not sure if it is important:

Do not run Composer as root/super user!

The next thing, I get this error:

the requested PHP extension gd is missing

I have the feeling that I should probably add a line to install the extension before I install composer or load a Docker image with that installed...?

Now Im not sure I understand what you do next, the vendor/phpunit and the artifacts part?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

bitbucket-pipelines

drupal