Nice improvement from Woodpecker CI Update
A few months ago, I wrote about my CI setup for my Smokeweb project, and how I had to take a few workarounds to make it work. And recently, Woodpecker release v3.16.0 fixed a couple of the issues I had. 馃帀 If you recall, my main issue was that I couldn鈥檛 use Woodpecker鈥檚 Service feature. That was due to the fact that I鈥檓 using a Ceph RBD StorageClass to provide the pipeline volumes. And those are RWO by nature, meaning they can only be mounted on a single node of my k8s cluster. This, ultimately, meant that if the service for running my test Postgres instance got scheduled on a different node than all of the pipeline steps, there would be a deadlock. The steps won鈥檛 be able to start because the pipeline volume is already mounted on the node the Service is running on. ...
