From d8c9562d598a0d10670c702b5afb964240218b3d Mon Sep 17 00:00:00 2001 From: "Kevin Reiss." Date: Thu, 6 Jun 2024 12:27:56 -0500 Subject: [PATCH 1/3] Add deployments to runner role. --- runner.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/runner.md b/runner.md index 9868c82..9f8cccd 100644 --- a/runner.md +++ b/runner.md @@ -4,7 +4,7 @@ title: Runner role --- # Runner role -The runner role switches off between team members each week. The runner should be somebody who is planning to be in for the whole week. +The runner role switches off between team members each week. The runner should be somebody who is planning to be in for the whole week. The runner as executes a deployment of all our applications to staging and production during the course of their week as the runner. ## Initial setup @@ -85,3 +85,10 @@ If you are a libanswers admin, you may follow this procedure to block an email a 5. Press the "Add Block" button. If you are not a libanswers admin, Vickie can block the email address for you. + +## Deployments + +The runner executes a production and staging deploy of each of our DACS applications. + +1. Go to [Ansible Tower](https://ansible-tower.princeton.edu/). +2. Execute a [Deployment with Capistrano](https://ansible-tower.princeton.edu/#/templates/job_template/13/details) for each [DACS application](https://docs.google.com/spreadsheets/d/1fJZ6CE4yq4EyaoeOE__bjEYPUv5xlZVM0bPKfyVAUQw/edit#gid=0) for those applications that have a staging and production environment. From b83fa0ffde5238e603319605352900a94bec7d6b Mon Sep 17 00:00:00 2001 From: "Kevin Reiss." Date: Thu, 6 Jun 2024 16:23:11 -0500 Subject: [PATCH 2/3] Deployments are managed by the Board Manager. --- board.md | 11 +++++++++++ runner.md | 9 +-------- 2 files changed, 12 insertions(+), 8 deletions(-) diff --git a/board.md b/board.md index cb771f2..769aaab 100644 --- a/board.md +++ b/board.md @@ -20,6 +20,7 @@ Here are descriptions of some of the columns on the board: | Review/QA | Issues typically attached to a pull requests that need review or other input from DACS team members before they can be closed | + ## Story points When using Epic tickets do not actually assign points to the ticket itself, Epics are the sum of the points of their assigned individual tickets. @@ -32,3 +33,13 @@ When using Epic tickets do not actually assign points to the ticket itself, Epic |5 points|2-3 days| |8 points|1 week| |13 points|Needs to be broken down into smaller tickets| + +## The Board Manager Role +Every sprint a different team member rotates to the role of "board manager". This individual shares the board with the team during stand-ups and planning meetings and leads us through a discussion of the board. The board manager role should be assumed by a Team member who plans to be in the office for entire sprint. The board manager also executes a deployment of all our applications to staging and production during the course of their week as the board manager. + +### Deployments as the Board Manager + +The runner executes a production and staging deploy of each of our DACS applications. + +1. Go to [Ansible Tower](https://ansible-tower.princeton.edu/). +2. Execute a [Deployment with Capistrano](https://ansible-tower.princeton.edu/#/templates/job_template/13/details) for each [DACS application](https://docs.google.com/spreadsheets/d/1fJZ6CE4yq4EyaoeOE__bjEYPUv5xlZVM0bPKfyVAUQw/edit#gid=0) for those applications that have a staging and production environment. diff --git a/runner.md b/runner.md index 9f8cccd..2ea24d5 100644 --- a/runner.md +++ b/runner.md @@ -4,7 +4,7 @@ title: Runner role --- # Runner role -The runner role switches off between team members each week. The runner should be somebody who is planning to be in for the whole week. The runner as executes a deployment of all our applications to staging and production during the course of their week as the runner. +The runner role switches off between team members each week. The runner should be somebody who is planning to be in for the whole week. ## Initial setup @@ -85,10 +85,3 @@ If you are a libanswers admin, you may follow this procedure to block an email a 5. Press the "Add Block" button. If you are not a libanswers admin, Vickie can block the email address for you. - -## Deployments - -The runner executes a production and staging deploy of each of our DACS applications. - -1. Go to [Ansible Tower](https://ansible-tower.princeton.edu/). -2. Execute a [Deployment with Capistrano](https://ansible-tower.princeton.edu/#/templates/job_template/13/details) for each [DACS application](https://docs.google.com/spreadsheets/d/1fJZ6CE4yq4EyaoeOE__bjEYPUv5xlZVM0bPKfyVAUQw/edit#gid=0) for those applications that have a staging and production environment. From 9526fff5461e8b373d9926adfe662f364f30afa7 Mon Sep 17 00:00:00 2001 From: Kevin Reiss Date: Mon, 8 Jul 2024 12:32:22 -0500 Subject: [PATCH 3/3] Update board.md Co-authored-by: Jane Sandberg --- board.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/board.md b/board.md index 769aaab..66ebde3 100644 --- a/board.md +++ b/board.md @@ -39,7 +39,7 @@ Every sprint a different team member rotates to the role of "board manager". Thi ### Deployments as the Board Manager -The runner executes a production and staging deploy of each of our DACS applications. +The board manager executes a production and staging deploy of each of our DACS applications. 1. Go to [Ansible Tower](https://ansible-tower.princeton.edu/). 2. Execute a [Deployment with Capistrano](https://ansible-tower.princeton.edu/#/templates/job_template/13/details) for each [DACS application](https://docs.google.com/spreadsheets/d/1fJZ6CE4yq4EyaoeOE__bjEYPUv5xlZVM0bPKfyVAUQw/edit#gid=0) for those applications that have a staging and production environment.