Release tracker

Introduction

Ever had one of your testers ask you if the release to test/acc/prod had been done yet?
Ever had no control over doing your releases and had to wait for a third party to finish doing it and you wanted to know if they did it correctly?

This is where Release Tracker comes in.

Set and keep track of a version of your Drupal site.

This module allows you to set a release-number as part of the Drupal configuration.
It contains a handy drush command to change the release-number.

This will allow you to determine if a new build was successfully released to the server and that the new configuration was imported just by looking at the status report page.

How to use

The current release number is visible on the status page. If the version is shown without errors but doesn't match your new release number, the new configuration was not deployed successfully. If the release number in the sync configuration doesn't match the release number in the active configuration an error will be shown in the status report that the active configuration is out of date. Run a configuration import to sync.

Update the release number and export config before tagging a new release. This will allow you to check on the live/staging server if your release has been successfully uploaded and imported.

The drush command release-tracker-bump (rtb) is available to bump the release number. You can use 'major', 'minor' or 'patch' (default) to specify the type of release bump you wish to do.

Example commands

Example workflow

$ drush release-tracker-set 2.5.0
Release set to 2.5.0

$ drush config-export -y
Differences of the active config to the export directory:

+------------+--------------------------+-----------+
| Collection | Config                   | Operation |
+------------+--------------------------+-----------+
|            | release_tracker.settings | Update    |
+------------+--------------------------+-----------+

 // The .yml files in your export directory (../config/sync) will be deleted and
 // replaced with the active config.: yes.                                      

 [success] Configuration successfully exported to ../config/sync.

$ git add .

$ git commit -m "Release 2.5.0"
[master c9e4e4035] Release 2.5.0
 1 file changed, 1 insertion(+), 1 deletion(-)

$ git tag 2.5.0

$ git push && git push --tags
Counting objects: 5, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (5/5), done.
Writing objects: 100% (5/5), 472 bytes | 472.00 KiB/s, done.
Total 5 (delta 3), reused 0 (delta 0)
To gitlab.com:dx-experts/dx-experts.git
   52d49cf0d..7d5b58f72  master -> master
Total 0 (delta 0), reused 0 (delta 0)
To gitlab.com:dx-experts/dx-experts.git
 * [new tag]             2.5.0 -> 2.5.0

Using the UI

You cannot change the release-number in the UI, that way nobody can manually fake the release.

Visit /admin/reports/status and view "RELEASE NUMBER" for the current version.