[michelvocks]

Thanks for the feedback. I will add that!

To answer your question, a pipeline is a real application which consists of at least one function (we call it job). You can compare it with a Jenkins Pipeline (https://jenkins.io/solutions/pipeline/). Therefore, a pipeline is one flow of automation task which consists of one or more steps.

[lalaithion]

"a pipeline is a real application which consists of at least one function"

So.... every application is a pipeline? This really clears very little up for someone not already familiar with the concept. The Jenkins link is about testing and deploying code. Is that the intended use case for this tool as well?

[0x8BADF00D]

I think they meant it is a replacement for existing CI/CD pipelines. As someone who deals with them every day, I like the simplicity of Gaia pipelines. But it seems it only supports running on the host that Gaia is installed on, whereas Jenkins and Gitlab CI will have the ability to run on multiple agents/build slaves.

Edit: gRPC for events is dope too.

[michelvocks]

It can be used as an replacement for existing CI/CD tools but not exclusive. In my opinion Gaia can be used for every possible automation task. :-)

We are already working on "agents/build slaves" (we call them worker): https://github.com/gaia-pipeline/gaia/issues/107

[0x8BADF00D]

Very cool. Will definitely keep an eye on your progress.