CI CD Workflows

Three Github Actions workflow are used for assisting in testing and deployment. The workflow files are located in .github directory. We currently have three workflows.

1. Dev

• When: A push is made to any Alloy branch or Konductor pushes to pre-prod.
• What: The workflow will test the Alloy branch's code against Konductor pre-prod.
• Why: Helps ensure that the Alloy changes will work with what Konductor will release.

2. Pre-deploy

• When: An engineer manually triggers the workflow before a release.
• What: The workflow will test the Alloy main branch against Konductor prod.
• Why: Helps ensure that what we're releasing will function properly when it reaches prod.
• Note: A badge will be shown in the readme for this workflow.

3. Prod

• When: On a schedule or when an engineer manually triggers the workflow after a release.
• What: The workflow will test that everything on prod is functioning as expected.
• When: Helps ensure that production is stable.
• Note: This is the only workflow that, when fails, will send a notification to Slack and email.

4. Pre-Edge-Deploy

• When: This configuration will be used by the Edge team to test against prod.