Skip to content

Campaign Cycle (CI CD)

Thomas edited this page Oct 1, 2025 · 4 revisions

Synopsis

CI/CD is essential so that we can actually make the engineering project possible.

We'll be having two different infrastructures:

  • GitHub Actions
  • VRIG Server(s)

GitHub Actions

We have GitHub actions so that we can continually run tests on all the pull requests and branches on the repository.

There's already some (if not all) of this implemented in the main repository, and it's free for us to run anyways.

VRIG Server(s)

This will be co-located with our databases to potentially run mini-campaigns with advanced logging to examine the behavior of changes.

I'm not sure currently who is owning/hosting/paying for this infrastructure, but we'll figure it out soon (is stack up??).

We'll be needing this CD stuff setup so we can ensure that our actual final campaign will go smoothly.

Unit Tests/Linting

Having unit tests would be great to ensure the proper functioning of our system.

Progress

GitHub Action stuff is already mostly in the repository.

No progress on VRIG Server(s).

Prior/External Work

Clone this wiki locally