Standardize Patterns for Different Releases

[sjonpaulbrown]

Problem Definition

Currently, when releasing software, we require a tag to be pushed to automatically build the Docker containers. There is often confusion around when, where, and why we push tags to build the containers, and furthermore, this is often manually handled if we decide a tag does not need to be pushed to the public repo. In general, we need to discover and define the different patterns for building containers, and we need to document and automate the processes. Below, I have listed some known patterns for releasing our software, but we should also poll the team for additional patterns.

Known Patterns

• Security Patches
• Standard Releases
• Pre-Releases (Canary Builds, Pentesting, etc)

Proposed Solution

1. Poll the Flow team to determine additional patterns for building and releasing our software
2. Create public and private GitHub Workflows with the proper triggers to support the known patterns
3. Document the patterns and distribute the documentation to the team so that everyone understands the when, where, and why

Notes

• If additional credentials are needed, feel free to work with the SRE team to get the credentials created and stored

[sjonpaulbrown]

@vishalchangrani, @zhangchiqing, and @peterargue, I am tagging you all for visibility.