We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

GitLab pipelines for every need: testing, documentation, and writing a paper

Formal Metadata

Title
GitLab pipelines for every need: testing, documentation, and writing a paper
Title of Series
Number of Parts
60
Author
Contributors
License
CC Attribution 3.0 Germany:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date2019
LanguageEnglish

Content Metadata

Subject Area
Genre
Abstract
Continuous integration/delivery (CI/CD) pipelines are easily available: it's bundled with GitLab, for example. They can be used for various purposes: automatically testing a codebase on every commit, building and deploying a package and many more. Using CI/CD pipelines have greatly improved workflows in a few of my projects. Based on these experiences, I would demonstrate a few use cases for CI/CD pipelines: (a) automated unittesting in a python software project, (b) scheduled integration tests, (c) automatically generating PDF manuscripts from LaTeX source.