Recommended patterns for New Project CI

[SterlingPeet]

Pattern

When a new team creates a new F Prime flight project (or any new project) there are a lot of decisions to make. It would be useful and helpful to fast track teams into a working CI process for their project.

Rationale

When CI is not considered early in the development process, many projects tend to develop a lot of technical debt around the testing. This is understandable given the exploratory nature of starting a new project and the lack of visibility without a default CI process.

For projects that know how they want to write their CI setup, understanding the expected or intended methodologies is helpful for crafting a synergistic process. For new and inexperienced teams, having default CI tooling help prevent undue technical debt while getting started with a working system.