The world changes around us!
Some of our code depends on the outside world (some even on stuff that is still fluctuating).
As an example I’ve just spend a day finding (and a couple of minutes fixing) a bug in one of our chef cookbooks that suddenly broke because of a change in the development version of Ubuntu (that will become a LTS version, so something we will probably run quite a few copies of). And I hit that because I changed something else in that chef cookbook, but couldn’t get on with that because the CI tests started failing.
It probably wouldn’t have saved me any work/time, but it would have saved some frustration if I hadn’t hit, and had to fix, a bug that was completely unrelated to what I was working on now - and I could if I had become aware of that change a month ago (when it was introduced). I would have if GitLab regularly rerun CI tests on this project. Can I make GitLab do that?