CI/CD

CI/CD (Continuous Integration & Continuous Delivery) means automating build, test, and release steps, so that integration problems are detected early. Each code change is frequently and consistently integrated and tested via a pipeline.

This prevents the infamous "integration hell" where everything has to come together at once at the end. Thanks to automation, the team gets quick feedback on new code (does the build work, do tests pass?) and a working version of the game is always available.

Starting points

• What is CI/CD?

Key points

• Setting up an automated build/test pipeline (e.g., via GitHub Actions, GitLab CI) that runs on every push or merge.
• A consistent, green build: the student monitors pipeline outcomes and immediately resolves any build errors or failing tests.
• Regular delivery of (intermediate) products: for example, playtests or builds are periodically shared with the team/stakeholders (continuous delivery), ensuring continuous insight into progress and quality.