"How do I deploy code from my local machine, or GitHub, to the Acquia Cloud?"
For information on how to deploy to production, see release-process.md.
This document outlines the workflow to build a complete Drupal docroot (plus supporting features, such as Cloud Hooks) which can be deployed directly to Acquia Cloud. Collectively, this bundle of code is referred to as the "build artifact".
The most important thing to remember about this workflow is that the Github and Acquia Cloud repos are not clones of one another. Github only stores the source code, and Acquia Cloud only stores the production code (i.e. the build artifacts).
Currently, this workflow can either be followed manually, or integrated into a CI solution such as Acquia Pipelines, Travis CI, or Jenkins.
First time setup¶
You should have your Github repository (where this document is stored) checked out locally. Your Acquia Cloud repository should be empty, or nearly empty.
Check out a new branch to match whatever branch you are working on in Github (typically
Ensure your Acquia Cloud remote is listed in project.yml under git:remotes.
Creating the build artifact¶
In order to create the build artifact in
/deploy, simply run
This task is analogous to
setup:build but with a few critical differences:
- The docroot is created at
- Only production required to the docroot
- (planned) CSS / JS are compiled in production mode (compressed / minified)
- (planned) Sensitive files, such as CHANGELOG.txt, are removed.
After the artifact is created, you can inspect it or even run it as a website locally. You may also manually commit and push it to Acquia Cloud.
Create and deploy the build artifact¶
To both create and deploy the build artifact in a single command, run the following command
blt deploy -Ddeploy.branch=develop-build -Ddeploy.commitMsg='BLT-123: The commit message.'
This command will commit the artifact to the
develop-build branch with the specified commit message and push it to the remotes defined in project.yml.
Modifying the artifact¶
The artifact is built by running the
deploy:build target, which does the following:
- Rsyncing files from the repository root
- Re-building dependencies directly in the deploy directory. E.g.,
The rsync and re-build processes can be configured using the
deploy Phing variable.
See Extending BLT for more information on overriding Phing variables.
Debugging deployment artifacts¶
If you would like to create, commit, but not push the artifact, you may do a dry run:
blt deploy -Ddeploy.branch=develop-build -Ddeploy.commitMsg='BLT-123: The commit message.' -Ddeploy.dryRun=true
This is helpful for debugging deployment artifacts.
Instead of performing these deployments manually, you can enlist the help of a CI tool such as Acquia Pipelines, Travis CI, or Jenkins. This will allow you to generate deployment artifacts automatically whenever code is merged into a given branch. Please see Continuous Integration for information on configuring a CI tool.
On Acquia Cloud, Cloud Hooks are the preferred method to run database updates and configuration imports on each deploy. BLT provides a post-code-deploy hook that will conveniently run these updates automatically and fail the deployment task in Insight if anything goes wrong.
To install Acquia Cloud hooks for your BLT project:
Initialize Acquia Cloud hooks
This will add a hooks directory in your project root based on BLT's default Acquia Cloud hooks.
Commit the new directory and push it to your Acquia git remote. Example commands:
git add hooks git commit -m 'Initializing Acquia Cloud hooks.' git push origin
For consistency and reliability, you should run the same updates on deployment as you would run locally or in CI testing. BLT provides aliases for the
setup:update task to support this, such as
deploy:update. These aliases all run the same updates, but with the appropriate aliases and configuration directories for each environment.
If your team uses Slack, you can also be notified of each successful or failed deployment. Simply set up an incoming webhook in your Slack team to receive the notification (see the API documentation at https://api.slack.com/), and then store the webhook URL in a
$HOME/slack_settings file on your Acquia Cloud servers:
For more information, see the Acquia Cloud Hooks Slack example.