A few years ago, I made a Telegram bot that I use daily to remind myself things I have to do: https://t.me/remembr_bot

You basically send it a message that says : "Pay water bill in two days at 9am", and it will send you a notification that says "Pay water bill" in two days, at 9am. You can also easily snooze notifications using handy quick-actions buttons.

It's free btw, anybody can use it.

Yeah it does work with includes. One of the pain point right now is that it does not work with cache:untracked or artifacts:untracked, but I'm trying to figure it out :)

Haha, I have nothing that relies on that, so should be fine for me.

I guess you do something like secretly make separate artifact folders per job and keep copying (or just linking) stuff around?

Yeah I thought about that, but gitlab-runner doesn't allow to "share" cache or artifacts between jobs so it's not a good fit to test multiple-jobs workflows.

Haven't test the tool yet. Neither do I know how close the behaviour of the pipeline locally will differ on the server.

Saying that, pipeline test tools are very much needed. Making commits and refreshing a UI is not practical.

I can test a distributed pipeline on spark why can't I do that with modern CI/CD?

Sure it does. Jobs have a shared cache (although this can be slow) and artifacts are shared to downstream jobs.

Maybe this is a tiered feature?

https://docs.gitlab.com/ee/ci/caching/

When using the "exec" command it doesn't do that. It just executes one job, not the whole pipeline.