Build Hooks

Synopsis

This module allows you to trigger a build hook on any service provider that supports build hooks.

The typical use case is for static sites built with Gatsby powered by the Gatsby Drupal source plugin.

This module mainly provides privileged users with a UI to:

- Trigger deployments of the connected static site(s) at will, or automatically via cron or when an entity is modified.
- View a log of the content that has been created, modified or deleted since the last deployment, by environment.

New 3.0 version!

The 3.0 version now supports Bitbucket Pipelines.

Which version should I use?

You should use the 3.x series. There are no API changes between 8.x-2.x and 3.x, just new features and a switch to semantic versioning.
The 2.x branch was a major rewrite of the module. Here is a list of main changes:

• add the possibility to add multiple "Frontend environments" to deploy to.
• add a system to log changes to specific content entity types, so that privileged users are able to know which and how many entities have changed on the site since the last deployment
• allow privileged users to choose per environment how the deployment should happen: manually, on cron or when one entity of the selected entity types is created/edited/deleted.
• Frontend environments are now plugins, so you can code your own including custom logic and custom configuration.

Existing integrations:

• Generic send a webhook to any service
• Netlify (provided in a submodule that ships with the module)
• CircleCI (provided in a submodule that ships with the module)
• Bitbucket Pipelines (provided in a submodule that ships with the module)
• Microsoft Azure Dev OPS (provided by the Build Hooks Azure module)
• Travis CI (provided by the Travis build (2.x) module)

An upgrade path is not provided: if you want to upgrade from the 1.x version to the 2.x version please just unistall, upgrade and install again.