Help us improve the GitPulse documentation. Fill in the survey.

Thesis goals

  • For: Everyone
  • Requires: Nothing
This page lists the sub-tasks of the master’s thesis Tools for Supporting DevOps Fundamentals Teaching as stated in the task formulation (Section 1.2 of the thesis) and links the chapters that address them.

Source. The authoritative source is the thesis text in the dp.mykyta.olym/thesis repository. A short overview of the chapters is in the Thesis section.

Sub-tasks

#TaskChapterStatus
1Analyse the team assignment requirements and separate conditions a program can check from those the teacher judges.2. Analysis of the team assignmentsDone
2Examine existing tools for automated assessment, repository analytics and change checking.3. Existing toolsDone
3Verify which data GitLab sends through webhooks and which must come from the REST API, and set the limits of interpreting them.4. Getting data from GitLabDone
4Design the architecture, data flow and security boundaries of a platform that does not touch student repositories.5. Design of the GitPulse platformDone
5Build a prototype with course import, synchronisation, configurable checks and overviews.6. ImplementationDone, running on the public instance
6Design an evaluation that separates technical correctness from pedagogical effect and prepare it with the target group.7. Evaluation methodsMethod ready, measurements in winter 2026/2027 and from February 2027

Tasks and this documentation

Design principles

  1. Event-driven. GitPulse receives GitLab webhooks and fetches details through the REST API. Nothing changes on the GitLab side and student repositories are only read; only the optional classroom assistant writes, under the course’s own account.
  2. A student over a term. Checks R01 to R13 follow a student’s work across their merge requests, not a single change.
  3. The teacher decides. A check result carries an explanation and a link to GitLab and is not a grade.