Hey. My too cents here. I am building DSCI - self hosted git with ci embedded . Suitable for small teams with limited VPS hosting, features:

• general programming languages for ci ( not YAML )

• super simple install and maintaining- everything is a single binary ( golang ) , ci jobs run on localhost/podman/docker

• no need extra runners / k8s / devops teams - everything is in dev hands through regular programming code - super simple

• ci SDK is available for bash/python/perl/raku/php/powershell/golang

It’s still in early development stage , but users can already play with it - here is demo stand - http://dsci.sparrowhub.io/

Documentation is available here - http://deadsimpleci.sparrowhub.io/ or GitHub - https://github.com/melezhik/DSCI

See installation page on podman specific setup … Pretty much the same as docker

Example of dsci pipeline - https://forgejo.sparrowhub.io/root/test/src/branch/main/.dsci

You may try out https://github.com/melezhik/sparky which is a local / remote task runner with nice front end and scripts could be written on many languages

Ok. “I am a good FOSS developer”

Thanks, will take a look

nano is the best (imho) for up to medium size files. It’s preinstalled in most Linux boxes , it’s simple and flexible enough, takes a minimal amount of time to learn basic for keys and then use them all the time

Yep. Like said - “We talk about use of Bash for simple enough tasks … where every primitive language or DSL is ok”, so Bash does not suck in general and I myself use it a lot in proper domains, but I just do not use it for tasks / domains with complexity ( in all senses, including, but not limited to team work ) growing over time …

We are not taking about use of Bash in dev vs use Bash in production. This is imho incorrect question that skirts around the real problem in software development. We talk about use of Bash for simple enough tasks where code is rarely changed ( if not written once and thrown away ) and where every primitive language or DSL is ok, where when it comes to building of medium or complex size software systems where decomposition, complex data structures support, unit tests, error handling, concurrency, etc is a big of a deal - Bash really sucks because it does not allow one to deal with scaling challenges, by scaling I mean where you need rapidly change huge code base according changes of requirements and still maintain good quality of entire code. Bash is just not designed for that.

Let me generalize that - yaml pipelines are terrible 😀