Docker Swarm is arguably the simplest, yet still highly effective, orchestration solution for containerized applications.

Last week marked the release of the new major version of the Spring Boot. Migrating application to a new version of the framework is never a straightforward process. So, check out my experience of going through this exercise.

Let's take a look into three more advanced use cases for Buildkit in Jenkins pipeline. How we can improve performance of the Buildkit build? How can Buildkit help you to run unit tests and extract their results while building Docker image? How can we scan the Docker Image from pipeline without pushing it to the registry?

How you build your Docker Images with Buildkit if your organization is obsessed with their own SSL Certificate Authority and only allows access to the internet via corporate proxy?

As it was announced in 2020, Kubernetes deprecates Docker as container runtime in v1.20 and it will be removed starting from v1.24 which is getting released soon. In case your Jenkins pipelines are using the Kubernetes plugin it is highly likely that pipelines are using underlying Docker to build images, hence you might have a problem.

Imagine yourself in the middle of a busy IT company that develops a software system. In a large number of cases, such a system will be using some form of the database at the backend. This means that you will likely face a major problem during development, test and subsequent production use: how to keep the database uniform and up to date across various environments? Another big issue that comes out the above is how to provide developers with the disposable copy of the database that is preloaded with some test data. If you struggle to solve either of the above issues you’re in the right place. I explain how to deal with both of these problems using the combination of the unlikely tools: Liquibase and Docker.