morphy VS engine

This is so true but my biggest struggle. Everything I have just shipped before I thought it was ready did really well, yet I still struggle to do it. I built my own static site generator, which I use for my own blog: https://github.com/kiramclean/morphy

I need to at least add documentation, and obviously there's a million other things I think I need before I tell anyone else about it.

I recently set up code coverage reporting with Codecov for a Clojure project of mine that uses tools.deps and builds on CircleCI. It turned out to be pretty easy but the documentation for the various parts was a bit ambiguous, so I wrote down the steps here in case you're looking to do the same. You can see all the changes it took together in context in this commit where I set it up for my project.

It's a pipeline engine for Kubernetes[1]. The idea is to build a tool that can be flexible enough for CI/CD, but also used for other things such as for example data processing.

The pipelines are just designed as serial and parallel execution of pods with no fancy features (i.e. loops or conditions) and the idea is to let other tools generate more complex pipelines using code.

Responsibility of triggering the pipelines is decoupled to standalone controllers such as github-screener[2] which enables triggering of pipelines used for CI/CD.

The project currently builds itself, but the docs are a bit outdated and there's quite a lot progress to be made.

[1] https://github.com/kuberik/engine