Update Trigger Build

Detects when new releases of Drupal are available and triggers a build on a continuous integration server. This can be used as part of a continuous integration pipeline where upgrades are carried out automatically by the CI server - very useful for promptly responding to security releases like Drupalgeddon, especially when you manage a large network of sites.

Build triggers are flexible and it's possible to choose whether security upgrades only should trigger a build and also whether core, modules or themes should act as a trigger.

Jenkins CI Server is supported out of the box and the module can be extended to work with additional CI server types, such as Travis, Go or others.

If you like to keep the Update module disabled then that's ok! This module will enable Update when needed and disable when the update check is complete.

Instructions for Use

- Enable update_trigger_build and update_trigger_build_jenkins
- Go to /admin/config/development/update_trigger_build and follow the instructions.

Upgrade Instructions

- When upgrading from 1.0-beta2 or below, ensure that you visit /update.php and run the database upgrade.

Developers

The module makes use of the Entity API, so creating a new CI Server type is possible by creating a new entity that is a bundle of the CI Server entity. See update_trigger_build_jenkins module (in src/CIServerTypes/Jenkins) for an example.

If you want to create a new CI Server type the best tactic is to copy the update_trigger_build_jenkins module and adapt as required. There are verbose comments in the module.

If you find that update_trigger_build needs to be adapted to support your CI Server type then open an issue.

Credit

Developed by College of Medicine, Dentistry and Nursing and College of Life Sciences at the University of Dundee.