Active Update to Repository with 6 Linux and 2 Windows Runners

On 12th March, 2025 we have reinstalled our runners. Runners are those which compile the project in its development environment and release key data that is crucial to the project's stability and testing. We are testing the project on 6 Linux VMs which compile the codebase in both GCC and Clang environments, each having Debug and Release configurations. Debug and Release configurations are the two different kind of configurations that the project can be compiled in. Debug means the project will hold debug information in its compiled state, while Release means a more optimized version of the software is compiled. Both these configuration was well as RelWithDebInfo are an important configuration for the project to be compiled in each runner pipeline.

An example of a runner can be seen inside the laboratory each commit will have a check mark of whether it is passed or failed. Passed indicates a good working state of the project, while fail means a cross mark in red. Both these states are declared by each of the runners. That is why the runners are an important part of the project's development. For example, take a look at the image below -

Each job has either passed or failed or is currently being worked on. These are automations which compile the code as and when it is pushed to the repository. Having this in our project simply boosts the quality and performance of the system.