We have a multi-site Drupal install set up on Acquia Cloud and have a local development team building out a site, this development work is version controlled in one of our own Github repos. This repo is connected to CircleCI, but currently CircleCI only runs the default Behat/PHPUnit tests on Pull request, it does not build a deployment artifact or push to the Acquia cloud git repo.
I am trying to understand what the best workflow is for the develop branch in our Github repo to be deployed to the development environment in Acquia cloud. In this scenario the developers building the site are not the same people pushing the changes to Dev.
I've had a look at a few examples of
config.yml files such as https://github.com/fourkitchens/example-acquia-8-composer-circle2/blob/master/.circleci/config.yml but these use Composer. I'm thinking that we need to modify the yml file to run BLT commands which then in turn drive composer rather than explicitly run 'composer install' for example.
I can see what looks like useful documentation at https://blt.readthedocs.io/en/latest/deploy/ and https://docs.acquia.com/tutorials/deploy/generating-deployment-artifact/ regarding setup for
blt.yml and then generating a deployment artifact, but I'd really appreciate some advice on stitching it all together from the moment a PR is accepted to our Dev branch through to getting it on Acquia development server.