Skip to content

Commit

Permalink
Deployments are managed by the Board Manager.
Browse files Browse the repository at this point in the history
  • Loading branch information
kevinreiss committed Jun 6, 2024
1 parent d8c9562 commit b83fa0f
Show file tree
Hide file tree
Showing 2 changed files with 12 additions and 8 deletions.
11 changes: 11 additions & 0 deletions board.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand All @@ -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.
9 changes: 1 addition & 8 deletions runner.md
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down Expand Up @@ -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.

0 comments on commit b83fa0f

Please sign in to comment.