<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>ci on bascht.com</title><link>https://bascht.com/tags/ci/</link><description>Recent content in ci on bascht.com</description><generator>Hugo -- gohugo.io</generator><language>de-de</language><lastBuildDate>Thu, 08 Apr 2021 00:00:00 +0000</lastBuildDate><atom:link href="https://bascht.com/tags/ci/index.xml" rel="self" type="application/rss+xml"/><item><title>Kubernetes Docker dind MTU issues on Hetzner (Cloud)</title><link>https://bascht.com/tech/2021/04/08/kubernetes-docker-dind-mtu-issues-on-hetzner-cloud/</link><pubDate>Thu, 08 Apr 2021 00:00:00 +0000</pubDate><guid>https://bascht.com/tech/2021/04/08/kubernetes-docker-dind-mtu-issues-on-hetzner-cloud/</guid><description>(angrily-typed-after-a-wasted-night-of-debugging)
Recently we used Hetzners new vSwitch subnets to start adding dedicated servers to one of our Kubernetes Clusters. Especially for CI workloads where we don&amp;#39;t need persistent storage, this is really cost-effective, as we could basically replace 4 other worker nodes with a single cheaper node.
Upon spawning the first GitLab runner pods on the new node things went south: We saw random build failures bubbling up in jobs that didn&amp;#39;t fail for ages:</description></item><item><title>Better GitLab Pipeline UX with custom CSS</title><link>https://bascht.com/tech/2020/11/18/better-gitlab-pipeline-ux-with-custom-css/</link><pubDate>Wed, 18 Nov 2020 00:00:00 +0000</pubDate><guid>https://bascht.com/tech/2020/11/18/better-gitlab-pipeline-ux-with-custom-css/</guid><description>Here&amp;#39;s a quick Firefox Stylus trick for GitLab CI users:
If you want to highlight certain rollout jobs (think: production or beta rollouts), in the pipeline overview you can do so by matching the id element. Here&amp;#39;s my custom CSS I apply to GitLab:
.gl-label { border-radius: 0.35rem } .pipeline-graph .build { width: auto; } .pipeline-graph .gl-text-truncate { overflow: visible; } .pipeline-graph .build .build-content { border-radius: 10px; } .</description></item><item><title>Continuous Integration mit Symfony</title><link>https://bascht.com/blog/2009/02/09/continuous-integration-mit-symfony/</link><pubDate>Mon, 09 Feb 2009 00:00:00 +0000</pubDate><guid>https://bascht.com/blog/2009/02/09/continuous-integration-mit-symfony/</guid><description>Auf Wunsch eines einzelnen Herren werde ich mal kurz den Stand meiner Forschungsarbeiten auf dem Gebiet Continuous Integration mit Symfony festhalten. Skoop (Stefan Koopmanschap) hatte bereits seit einiger Zeit einen Proof of Concept für die Integration von lime in das von phpUnderControl benötigte XML-Format geschrieben - der wurde jedoch nie released. Nun ists endlich soweit - Version 0.0.1 des symfonyUnderControlPlugin liegt im Repo. Also, frisch ans Werk - Plugin eingebunden - Task probiert - Fehler.</description></item></channel></rss>