CI/CD YAML syntax reference

iOS engineering, CI infrastructure, and personal essays by Thuyen Trinh.

Learn how to securely upload Python packages to PyPI from GitLab CI/CD pipelines using a “Trusted Publisher” (and without API tokens). Continuously test the release process with TestPyPI on every push. Use GitLab (deploy) environments as an additional...

We had pipelines that ran for almost an hour.

Software engineering, open source and computer security

Continuous integration with GitLab for multi-module repositories.

Personally, I prefer to set up my own Gitlab Runners. The reasons being that I don’t have to wait for a runner to become available and they’re usually faster then the Gitlab Shared Runners.

Managing CI scripts across multiple GitLab projects driving you crazy? We share a battle-tested method for centralizing common GitLab CI scripts. Learn how to simplify maintenance, ensure consistency, and streamline your CI/CD process across projects - a technique we've successfully implemented in numerous deployments.

This time I’d like to touch on a few more advanced topics related to GitLab CI. The common theme here is implementing custom features within your pipeline. Again, most of the tips are specific to GitLab, but some could be easily applied in other CI systems as well. Running integration tests Checking your code with unit tests is usually easy to plug into any CI system.

Previously I detailed how I set up blog.winny.tech using GitHub for source code hosting and Caddy’s git plugin for deployment. This works well and I used a similar setup with my homepage. The downside is I host the static web content and I am tied to using Caddy.1 I imagine simpler is better, so I opted to host my static sites — https://winny.tech/ & https://blog.winny.tech/ — with GitLab pages. What’s wrong with Caddy?

Automatic and continuous testing is a fundamental part of today’s development cycle. Given a Gitlab pipeline that runs for each commit, we should enforce not only all tests are passing, but also that a sufficient number of them are present.

JetBrains Qodana is a new product, still in early access, that brings the “Smarts” of JetBrains IDEs into your CI pipeline, and it can be easily integrated in GitLab.

Shing Lyu's blog

À E-voyageurs Technologies, je travaille au sein d'une équipe en charge de l'usine logicielle, qui administre depuis plusieurs années une instance Gitlab self-hosted. Cet article contient quelques-unes de nos recommandations à l'intention des utilisateurs de notre Gitlab, ayant pour but à la fois améliorer les performances de leurs pipelines …

In a .gitlab-ci.yml job, if you do not specify a tag for an image, the latest tag is used by default. The default configuration of the gitlab-runner to pull Docker images is if-not-present, which means the image is only loaded if it is not already present. This in turn …

I think all technical writers, at some point or another, feel the urge to base their work on something more systematic than “it’s just the way folks documented stuff since forever”. Toolkits and frameworks provide content types, which is immensely valuable when you know what you want to write, but starting from there is like buying a hammer without knowing that half of the work you’ll do is turning screws. As I find the lack of deeper conversation around this topic rather unsettling, I decided to contribute some verses.

Split up test runs across multiple runners through counted partitioning or hashed sharding.

Step-by-step guide covering how to automatically deploy a Jekyll site to Netlify using Docker and GitLab CI.