From ae99d3c8b6af6a8dd6b7a47f75548881975a40e9 Mon Sep 17 00:00:00 2001 From: Ben Neill Date: Mon, 21 Jun 2021 13:35:06 +0100 Subject: [PATCH 1/2] Add in application path to production process --- ...pplication-approval-production.html.md.erb | 41 +++++++++++++++++++ 1 file changed, 41 insertions(+) create mode 100644 source/ways-of-working/path-to-live/application-approval-production.html.md.erb diff --git a/source/ways-of-working/path-to-live/application-approval-production.html.md.erb b/source/ways-of-working/path-to-live/application-approval-production.html.md.erb new file mode 100644 index 00000000..8112bfb2 --- /dev/null +++ b/source/ways-of-working/path-to-live/application-approval-production.html.md.erb @@ -0,0 +1,41 @@ +--- +title: Application approval into Production +last_reviewed_on: 2021-06-21 +review_in: 6 months +--- + +# <%= current_page.data.title %> + +This page explains the typical processes an application team must ensure they/their app has been through before getting the green light to deploy to production + +1. OAT - Operational acceptance testing covers multiple topics to try and ensure that your application is ready to go into production, it evidences topics such as best practices, avoiding anti-patterns, scalability, disaster recovery etc. + +you will need to contact the Release and Transition team with a proposed go live date and they will create the templated tickets for your consumption. + +Platform Operations ask for a few weeks notice and a few weeks leeway from your desired go live date. + +Platform Operations role in OAT is to raise any risks that the application might pose on any of the topics covered in the OAT and + +[OAT Ticket Sample](https://tools.hmcts.net/jira/browse/RBC-7754) + +2. ITHC + +an IT Health check is akin to a penetatration/vulnerability scanning test conducted by the Security team + +3. Tech Readiness Sign Off + +After OAT & ITHC is completed and usually 1-2 weeks before the proposed go live date, a tech readiness call will be arranged and chaired by the Release and Transition team + +The tech readiness is a chance for Business/Product Owners, Platform Operations, Programme Leads, Security and Release and Transition to raise any risks or approve the release for production + +4. Authority to Operate + +an Authority to Operate or AtO will be given after a successful ITHC and subsequent approval from the Tech Readiness meeting, this is granted by the CISO + +Best Practices: + +We discourage big bang deployments and encourage deploying components like infrastructure earlier than the proposed release dates to streamline the go live and as an opportunity to catch any unknowns ahead of the release date + +For application deployments to production via Jenkins you will need your repo included here [Environment Approvals] (https://github.com/hmcts/cnp-jenkins-config/blob/master/environment-approvals.yml) + +For infrastructure deployments via Jenkins you will need to have a read through [Terraform Infra Approvals] (https://github.com/hmcts/cnp-jenkins-config/tree/master/terraform-infra-approvals) and seek approval way ahead of time \ No newline at end of file From 8ce5736ef669081915b22be931bd890dbfda36ba Mon Sep 17 00:00:00 2001 From: Ben Neill Date: Mon, 21 Jun 2021 14:41:12 +0100 Subject: [PATCH 2/2] Update source/ways-of-working/path-to-live/application-approval-production.html.md.erb Co-authored-by: Tim Jacomb <21194782+timja@users.noreply.github.com> --- .../path-to-live/application-approval-production.html.md.erb | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/ways-of-working/path-to-live/application-approval-production.html.md.erb b/source/ways-of-working/path-to-live/application-approval-production.html.md.erb index 8112bfb2..bf0a0320 100644 --- a/source/ways-of-working/path-to-live/application-approval-production.html.md.erb +++ b/source/ways-of-working/path-to-live/application-approval-production.html.md.erb @@ -6,7 +6,7 @@ review_in: 6 months # <%= current_page.data.title %> -This page explains the typical processes an application team must ensure they/their app has been through before getting the green light to deploy to production +This guide explains the typical processes an application team must ensure their app has been through before getting the green light to deploy to production 1. OAT - Operational acceptance testing covers multiple topics to try and ensure that your application is ready to go into production, it evidences topics such as best practices, avoiding anti-patterns, scalability, disaster recovery etc. @@ -38,4 +38,4 @@ We discourage big bang deployments and encourage deploying components like infra For application deployments to production via Jenkins you will need your repo included here [Environment Approvals] (https://github.com/hmcts/cnp-jenkins-config/blob/master/environment-approvals.yml) -For infrastructure deployments via Jenkins you will need to have a read through [Terraform Infra Approvals] (https://github.com/hmcts/cnp-jenkins-config/tree/master/terraform-infra-approvals) and seek approval way ahead of time \ No newline at end of file +For infrastructure deployments via Jenkins you will need to have a read through [Terraform Infra Approvals] (https://github.com/hmcts/cnp-jenkins-config/tree/master/terraform-infra-approvals) and seek approval way ahead of time