Patterns

The ProCICD framework uses several patterns, akin to software design patterns, that reflect useful approaches to addressing common CICD requirements. In many cases, the elements in the base library can be copied and used as provided to implement the pattern; in other cases custom implementations are required.

Documented patterns include:

• Centralized Globals
• Including other files
• Custom job images
• Job labels
• CICD State
• Constants
• Variable setenv/getenv
• Version numbering
• Phase skipping
• Pipeline conditions
• Static docs sites

TODO: Add pattern for variables as error messages, outputting commands before running, etc