Goals
- Use Circle CI to automatically track and pull in new changes from github on the test sites, but not production.
- Sync production database with dev database on demand.
- Nice-to-have: Automatically move to new branch?
- Long term: Add bhat tests and a linter (done by April)
Background and strategic fit
The end of life of Drupal 7 is 2020. We have many big Drupal projects on the way, we should update our development pipeline
Assumptions
- This is for the Drupal devs only, including Oregon Explorer devs. This will not impact users.
- Stakeholders for drupal sites will be able to easily check in on the development process of their updated sites.
Requirements
# | User Story Title | User Story Description | Priority | Notes |
---|---|---|---|---|
1 | ||||
User interaction and design
Questions
Below is a list of questions to be addressed as a result of this requirements document:
Question | Outcome |
---|---|
Not Doing
- This setup assumes no AWS hosting for the drupal sites. This project will need to be revisited if the Drupal servers move to AWS or Pantheon.