Managing user services by systemd in Github Actions runners is not so obvious as in your local machine. Here is what I found when I was trying to start rootless podman as a service.

Web UI testing is a tricky thing in many aspects. They requires many dependencies, they are slow and they are often flaky. In this post I would like to share my web UI testing experience on an example of one python library.

Often when you want to run some tests you need to install required dependencies such as python packages, ruby gems, npm packages and so on. Nowadays tests are executed automatically for pull (merge) requests in various CI systems. Dependency pulling is repeated again and again for every test run and it takes time. We cannot do much about it in cloud based CI systems such as Travis, Circle CI or Github Actions but there is some space for improvement for self-hosted Gitlab CI, Jenkins and others.

Imagine you have a group of repositories in Gitlab and you would like to have the same pipelines for whole group.

I guess everybody knows Jenkins. It's one of the oldest and well-known automation system. It was developed in the times when there was no Docker, Kubernetes, cloud native and other buzzwords. I familiarized with it when I started to work at Red Hat. After a couple years of using I have some concerns I want to share.

I'm pretty sure most of you familiar with Gitlab. It has a lot of features and nowadays it looks a bit bloated but one thing I really love in this tool. It's Gitlab CI. One of the coolest thing there is it can run jobs on many platforms including virtual machines, Docker containers and Kubernetes.