Continuous Integration

note

Ed-Fi continuous integration (CI) practices and procedures

Overview

1. Utilize CI and automation wherever possible.
2. Infrastructure as Code (IaC) is critical, though we have some legacy exceptions (most relevant: old Octopus Deploy configurations).
3. "Continuous Deployment" (CD) is less relevant for Ed-Fi software, since we're providing software for other organizations to use. However, we do have a true CI/CD pipeline for the ODS Platform team.
4. As of 2022, we are shifting from TeamCity to GitHub Actions.

Child Pages

📄️ Code Quality Automation

Guidance for automating code quality checks.

📄️ Code Security Guidelines

Guidelines and policy for code security.

📄️ Example of CodeQL Detecting Dangerous Code

This example comes from the Meadowlark R&D project. In that project, the

📄️ Dependency Security Automation

Guidance for open- and closed-source projects.

📄️ Guidelines for Use of GitHub Actions

Goals, best practices, and policies.

📄️ Repository Scoring

Transparency and improvement through automated scoring.