Deployment process

Date adopted: 
August 28, 2020
Last update: 
August 28, 2020

What does deployment mean?

When we talk about deploying code, we mean the steps and processes we follow to make a service or website available to the public.

Onboarding vendors

eServices onboards all vendors on the eServices Standing Offer Agreement (SOA) list. They're aware that we have a code review and deploy processes as part of delivery services and websites to the public.

Once you've hired a developer and they begin work on your project, eServices will meet with them to determine how a service or website should be built and what approach the developer should take. This includes agreeing on how we'll tackle code reviews and deploys for your project.

Timing your deployment

The nature of your project will determine how many deploys there will be. After the code review process is complete, and the client and eServices confirm it, we'll have a 3rd party manage the deploy.

You can expect to deploy your service or website from Dev to UAT and UAT to Prod.

The code review and deployment process can take anywhere from a few days to 2 weeks.

Hiring a 3rd party to deploy code

eServices will work with the client and developer to determine how many rounds of code review and deploys your project will require. We'll then reach out to one of our pre-qualified, trained vendors to coordinate the deployment.

The department will approve the code review and deploy budget and eServices will get the contract in place.

Deploying after code review

Once the code review is complete and the client department is satisfied, eServices will work with the 3rd party developer to deploy the service or website.