iBOTS
GitLab CI/CD
GitLab's built-in automation system for running tests, checks, builds, and deployments from repository changes.
Our View
GitLab CI/CD turns project expectations into repeatable checks, helping research teams catch broken tests, missing dependencies, and packaging problems before changes are merged.
Provisional positions are editorial proposals awaiting group review.
Teaching — Recorded in topic offerings; consult the dated event links for availability.
1 topics with recorded teaching · 0 past offerings · 1 upcoming offerings
Related themes: Scientific Computing
Related topics: Automating Research WorkflowsRobust and Reusable Software
Common use cases
- Run tests automatically for merge requests
- Build documentation, packages, or containers from Git commits
- Standardize project checks across a research team
Getting started
GitLab CI/CD runs automated jobs defined in a repository. A project can use it to test code, lint notebooks or scripts, build documentation, publish packages, or assemble deployable artifacts whenever code changes.
Why It Matters in Research Workflows
Automation gives collaborators confidence that a shared codebase still works after a change. For research software, even a small test suite or documentation build can prevent regressions from quietly affecting downstream analyses.
In Our Teaching
We discuss GitLab CI/CD alongside GitLab merge requests and agile project practices. It provides a concrete way to connect code review with reproducibility checks and project maintenance.