The following procedures are how external developers deploy their work to the eServices Platform infrastructure.
The following is an overview of the deployment workflow.
Developers are expected to build project within their local development environment.
Alpha and beta releases are deployed to the development environment for preliminary testing, validating merge request procedures are working, ultimately demonstrating that work product functions on the eServices Platform infrastructure.
User Acceptance (UAT)
Only Release Candidates and Beta versions that have been approved by eServices can be deployed to UAT. At this stage, further stakeholder testing can be conducted.
Approved Release Candidates can then be deployed to production.