Skip to content

CI/CD

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

This prevents the notorious “integration hell,” where everything has to be merged all at once at the end. Thanks to automation, the team receives quick feedback on new code (does the build work, do the tests pass?), and there is always a working version of the game available.

Starting Points

Key Considerations

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