2017 Deployment Strategy

Owned by Andrew Natoli
Last updated: Dec 02, 2017
1 min read
Status

DONE

StakeholdersEtienne Laurin Andrew Natoli Jim Van Fleet 
OutcomeHeroku
Due date
OwnerAndrew Natoli 

Background

Planning the build and release strategy for the new version of the application.

I wanted to raise this discussion a little earlier this year, especially while we're still "early" in the architectural design of the new application. 

Details

The new codebase is being built to support serving a different app based on the host that's being accessed.

We should be able to use MySQL or PostgreSQL; which ever we'd all prefer. 

Now that we're using Node, are there any less expensive and or simpler approaches than hosting on Azure and writing a playbook to manage the deployments?

Also, any considerations for CI / CD, as well as user acceptance testing? We still have Jenkins floating around in Azure from last year; do we want to keep that jenkins instance running, move it to a different host, or explore switching to a different host and or overall staging environment?

Once we have the individual plans finalized we can make JIRA tickets to take care of them in the future. 

Action items

  • Review and decide on hosting
  • Review and decide on CI / staging procedures and environments
  • Review and determine deployment strategy.