You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Deploying software is complex. It is too easy, if the deployments are manual (or even partially so) to miss steps. Hence, our challenge is to eliminate the human-in-the-loop from our deployment process.
How did we discover this problem?
We have seen, on the previous system, how complex it is to manage a large software stack that is not fully automated. We will not repeat this.
Job Story(s)
When code is merged into main via PR, I want a deployment to staging to run, so tests (E2E or otherwise) can be run in a production-like environment.
What are we planning to do about it?
We will implement, via Circle/CI, build, test, and deploy automation on all PR merges.
What are we not planning to do about it?
We... are not planning to not do it.
How will we measure success?
The content you are editing has changed. Please copy your edits and refresh the page.
We are using Circle/CI because it protects the secrets we need to protect. As part of our work, we should make sure to document what credentials we grant to Circle/CI (but not the values!), and make sure they are rotated on a periodic basis.
Process checklist
Has a clear story statement
Can reasonably be done in a few days (otherwise, split this up!)
Screen reader - Listen to the experience with a screen reader extension, ensure the information presented in order
Keyboard navigation - Run through acceptance criteria with keyboard tabs, ensure it works.
Text scaling - Adjust viewport to 1280 pixels wide and zoom to 200%, ensure everything renders as expected. Document 400% zoom issues with USWDS if appropriate.
The text was updated successfully, but these errors were encountered:
Problem
Deploying software is complex. It is too easy, if the deployments are manual (or even partially so) to miss steps. Hence, our challenge is to eliminate the human-in-the-loop from our deployment process.
How did we discover this problem?
We have seen, on the previous system, how complex it is to manage a large software stack that is not fully automated. We will not repeat this.
Job Story(s)
When code is merged into
main
via PR, I want a deployment tostaging
to run, so tests (E2E or otherwise) can be run in a production-like environment.What are we planning to do about it?
We will implement, via Circle/CI, build, test, and deploy automation on all PR merges.
What are we not planning to do about it?
We... are not planning to not do it.
How will we measure success?
Tasks
Security Considerations
Required per CM-4.
We are using Circle/CI because it protects the secrets we need to protect. As part of our work, we should make sure to document what credentials we grant to Circle/CI (but not the values!), and make sure they are rotated on a periodic basis.
Process checklist
If there's UI...
The text was updated successfully, but these errors were encountered: