Functionality of building isolated applications
The process of building isolated applications begins with the allow-list. The allow-list is a collection of applications that are eligible to take advantage of a faster CI pipeline.
The allow-list lives in a JSON file in the
vets-website repository. Entries in the allow-list have the following properties:
Root folder of application(s) that lives in src/applications.
Slack user group of the team that owns the application.
Enables continuous deployment when set to
Once an application directory is added to the allow-list, branches with changes exclusive to those applications will see faster CI workflow runs. Branches that include changes from non-application code, or applications that aren’t on the allow-list, will perform a full build and all unit tests as usual.
Application(s) on allow-list
Changed files in branch
A full build is executed, because non-application code was changed.
For isolated application builds, the
Unit Tests job in the
Continuous Integration workflow will only run tests belonging to the updated application(s). The
Cypress E2E Tests job will only run Cypress tests for the changed application(s) as usual, with the addition of the MegaMenu Cypress test, to ensure that the header is consistent across all applications.
Help and feedback
Create an issue ticket to suggest changes to this page