Submitting code to be reviewed and for deployment

The following procedures are how external developers deploy their work to the eServices Platform infrastructure.

Environments

The following is an overview of the deployment workflow.

Local

Developers are expected to build project within their local development environment.

Development

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.

Production

Approved Release Candidates can then be deployed to production.

 

Next: Git merge requests →

Last update:
May 23, 2017