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
Currently, we use the main branch to deploy to perf and release to deploy to staging and production. This means that the main branch isn't serving any purpose other than being a holding ground for perf deploys. In order to facilitate a smoother CI/CD pipeline, we want to deploy everything from main and get rid of the release branch.
Ticket is understood, and QA has been contacted (if the ticket has a QA label).
User Story(ies)
As a VA Notify developer I want to deploy to staging and production from main So that we can streamline our CI/CD process.
Additional Info and Resources
Acceptance Criteria
Github actions/workflows are updated to deploy from main instead of release
Github actions/workflows that cut the release branch are removes
All existing pipeline steps remain the same. (Approvals, for example)
This work is added to the sprint review slide deck (key win bullet point and demo slide)
QA Considerations
Verify that things still work as expected (tag is cut on main, main is deployed to higher envs, etc)
Potential Dependencies
The text was updated successfully, but these errors were encountered:
User Story - Business Need
Currently, we use the
main
branch to deploy to perf andrelease
to deploy to staging and production. This means that themain
branch isn't serving any purpose other than being a holding ground for perf deploys. In order to facilitate a smoother CI/CD pipeline, we want to deploy everything from main and get rid of the release branch.User Story(ies)
As a VA Notify developer
I want to deploy to staging and production from main
So that we can streamline our CI/CD process.
Additional Info and Resources
Acceptance Criteria
QA Considerations
Potential Dependencies
The text was updated successfully, but these errors were encountered: