Commit 013f7611 authored by dmanik's avatar dmanik
Browse files

All slides conceptualized. Titles are there.

parent 8fd806e7
Pipeline #98057 passed with stage
in 27 seconds
* Find texlive docker image.
* Add .gitlab-ci.yml
* talk about badges.
* Talk about test running policy: each commit/only master/only on tags...
* Talk about artifacts.
* talk about paper repo.
......@@ -6,7 +6,8 @@
\setbeamerfont{page number in head/foot}{size=\large}
\setbeamertemplate{footline}[frame number]
% start custom macros
......@@ -52,5 +53,55 @@
\begin{frame}{But I want the \code{unittests:passing} badge!}
\begin{frame}{Use case 2: integration tests}
We had some tests that ``simulates'' our deployed system, i.e.
\item Plugs together all the componenets in our project.
\item Spins up the server.
\item Creates a client.
\item The client fires a few hundred requests.
\item We check if the server was able to handle all these requests.
Running these tests didn't fit in the basic CI/CD paradigm:
\item Takes too long to run.
\item We didn't need this to run on every commit to every branch.
We wanted a nighly run of these ``integration tests'' on master.
\begin{frame}{How to set this up?}
\begin{frame}{Use case 3: writing a paper!}
\begin{frame}{How to set it up?}
\begin{frame}{But I like jupyter notebooks too!}
\begin{frame}{What more can/should one do with CI/CD pipelines?}
\item Multi project pipelines.
\item Run unittests on merge requests.
\item Skipping the pipeline on certain commits (e.g. changing the \code{README}).
\item Artifacts: (this is how I created this talk)
\item Publish your package to PyPi.
\item Upload the docs to \code{readthedocs}.
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment