k0.hswaw.net has, uh, issues now.

Signed-off-by: Rahix <rahix@rahix.de>

We want to run a linter on CI submission.

We also want to display nice error messages to the user. Thus,
annoyatron is born.

The flow is as follows:
 - a MR is submitted and triggers the 'lint' pipeline
 - annoyatron gets pinged over https that an MR requires attention
 - annoyatron starts running and waits until the MR's pipeline run
   succeeds or fails
 - the lint jobs either succeeds or fails
 - annoyatron notices the pipeline passed, and inspects its results to
   see if the lint pipeline failed or not.
 - annoyatron posts a comment, if necessary

q3k authored 5 years ago and rahix committed 5 years ago

In this change we modify the CI pipeline to use pre-built Docker images
for both build and deploy stages.  To this end, we create
`docker/{build-env,deploy-env}`, two directories containing Dockerfiles
describing how to build those images, and scripts to push them to a
Docker registry.

Currently, docker.card10.badge.events.ccc.de seems broken. Thus, we push
to the Warsaw Hackerspace Docker registry.  Since the Docker images will
be pulled rarely anyway (as they are cached by build nodes), any low
bandwidth-caused slowdowns will not be usually end up in the CI critical
path.

We also bump `.gitlab-ci.yml` to point to those new images.

Signed-off-by: Rahix <rahix@rahix.de>

Signed-off-by: Rahix <rahix@rahix.de>

Signed-off-by: Rahix <rahix@rahix.de>