It's not done right now, but that was my idea. So the composer.json is added (by commit I assume) in the Drupal-Test branch which is used to trigger the Pipeline as I understand it. where you would do the deployment, for example to the test environment. The artifacts part is to have the vendor folder (created by the composer install) in the next pipeline steps, e.g. If you don't need to / want to run phpunit tests, then you can skip that part. That totally depends on what you need in your specific case. Now Im not sure I understand what you do next, the vendor/phpunit and the artifacts part? As you have noticed, the image is where the pipeline runs in. Edit: Using `-ignore-platform-reqs` is not recommended, composer has some more info about trouble-shooting PHP version & extensions in their docker image read-me.Īlternatively choose a different docker image or create your own that has all the software needed. Or add it specifically to composer config platform in the composer.json. If you know that building the software (running the pipeline) does not require that php extension, you can either ignore all platform requirements on install: composer install -ingore-platform-reqs The requested PHP extension gd is missing It says that composer runs as root which is something you normally don't want if you do a `composer install` locally. Locally I could not reproduce the warning. More recent versions of composer should not display the root/super user warning inside Docker containers, but I have not tested on Bitbucket. ![]() If there is a reason why you did not considered to add it to the repository, this might be worth to review before continuing. 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. 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.Īs 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. ![]() What does build and deployment mean here? IIRC Drupal 8 is compatible w/ Composer, go for it. The build does the composer install, so yes, at least somewhere you should place your `composer.json` file. Bitbucket supports three environments for deployment (test, staging and production) so this looks fitting for your TEST & PROD use-case.
0 Comments
Leave a Reply. |