Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

deploy to staging via circle/ci on all merges to main #85

Open
4 tasks
jadudm opened this issue Jan 14, 2025 · 0 comments
Open
4 tasks

deploy to staging via circle/ci on all merges to main #85

jadudm opened this issue Jan 14, 2025 · 0 comments

Comments

@jadudm
Copy link
Contributor

jadudm commented Jan 14, 2025

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 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?

Tasks

Preview Give feedback

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
  • Has a clear story statement
  • Can reasonably be done in a few days (otherwise, split this up!)
  • Shepherds have been identified
  • UX youexes all the things
  • Design designs all the things
  • Engineering engineers all the things
  • Meets acceptance criteria
  • Meets QASP conditions
  • Presented in a review
  • Includes screenshots or references to artifacts
  • Tagged with the sprint where it was finished
  • Archived

If there's UI...

  • 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.
@jadudm jadudm added this to the ready for lato assessment milestone Jan 14, 2025
@jadudm jadudm added this to jemison Jan 14, 2025
@github-project-automation github-project-automation bot moved this to triage in jemison Jan 14, 2025
@jadudm jadudm moved this from triage to backlog in jemison Jan 14, 2025
@jadudm jadudm moved this from backlog to underway in jemison Jan 14, 2025
@jadudm jadudm moved this from underway to backlog in jemison Jan 14, 2025
@igoristic igoristic self-assigned this Jan 15, 2025
@jadudm jadudm moved this from backlog to underway in jemison Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: underway
Development

No branches or pull requests

2 participants