deploy to dev from any branch via circle/ci

[jadudm]

Problem

While it is true that we can test Jemison locally, we sometimes want to test in a production-like environment.

It should be possible, from any branch, to push a build to dev in cloud.gov.

How did we discover this problem?

The previous system lacked a dev environment. It also lacked the ability for developers to test their code locally. While Jemison addresses the latter, we do not yet have the former. Being able to test in production matters, especially early on, to make sure that infrastructure-related code works as expected.

Job Story(s)

When I want to test my code on cloud.gov, as a developer, I want to push one button to deploy, so I can be confident in my work.

What are we planning to do about it?

We do not know if this is possible in Circle/CI. This story assumes it is possible to deploy from an arbitrary branch.

We should confirm this, and if it is possible, then implement an automation that any dev can trigger to deploy their software to dev.

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

1. provide "one button" to trigger a build/deploy to dev
2. do not deploy if linting fails
3. do not deploy if tests fail
4. code is built and deployed via TF to dev

Security Considerations

Required per CM-4.

Similar to #85.

---

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.