System overview
The Intranet provides a service that can automatically test student code submitted to the intranet Git repositories.
Students work in a Git repository managed by the intranet to complete exercises. To submit their work, students usually create a Git tag (The required tag prefix is provided on the intranet). Post-submission, students can access a trace on the intranet, offering insights into the results of their code execution, including validated tests, failed tests, and any associated error messages.
This workflow is supported by Maas, which evaluates the student's code using configured containers and input parameters. The overall system looks as follows:
You get to configure a few aspects of this pipeline:
- The event which triggers a job run. This is defined within your activity YAML.
- The containers and a few inputs for MaaS (see above).
- How trace results are used to validate assignments.
MaaS makes heavy use of Docker. If you are not familiar with Docker you should check out Docker Curriculum, which provides a good introduction.