Content releases are initiated in one of two ways:
- Automatically, via this Github Action Workflow
- Manually, via the "Release content" page in the CMS.
The Content Release Github Action Workflow handles automatic content deploys.
It is currently set to execute weekdays at 9AM, 10AM, 11AM, 12PM, 1PM, 2PM, 3PM, 4PM, and 5PM.
The content release is also triggered based upon content updates in Drupal. The logic that controls when a build is triggered is at Drupal\va_gov_build_trigger\Service::triggerFrontendBuildFromContentSave().
Manual content releases are initiated from the "Release content" page in the CMS.
This page is constructed by the va_gov_build_trigger module. The page will differ slightly in presentation and significantly in the details of its operation depending on which environment hosts it.
The "Release content" page on the BRD production environment invokes the [same Github Action Workflow]https://github.com/department-of-veterans-affairs/content-build/actions/workflows/content-release.yml) as the automatic deploys. Accordingly the content build output should be identical.
The Jenkins job configuration is stored in Drupal settings.php. Here are the settings for production. Settings for other environments can be found in the *.settings.php files. The setting keys are:
$settings['va_gov_frontend_build_type'] = 'brd';
$settings['github_actions_deploy_env'] = 'prod';The "Release content" page on the BRD staging environment is currently disabled because the content release GHA workflow does not support any environment other than production.
To manually run the Content Release job:
- Go to https://github.com/department-of-veterans-affairs/content-build/actions/workflows/content-release.yml.
- Click "Run Workflow"
More documentation for the content build can be found here.
The Tugboat and local development (Lando, etc) versions of the Release content page do not trigger a Github Actions workflow. Instead, they check out the latest version (or a specified branch or release) of the frontend, build it, and then perform a content release.
For more information on creating or releasing content from a preview environment, see Environments.