11–20 of 69 posts
How does this manage processes? From the example code it looks like your pipeline keeps running?
Yeah, you definitely need a "What are pipelines?" section. From looking over the examples, my impression is this is some kind of job scheduler, like sidekiq.
We have already defined a "Q&A" section in our github README file (https://github.com/gaia-pipeline/gaia#questions-and-answers-...). Does this briefly answer your question or is still too vague?
I agree with other commenters that it would be really helpful to understand exactly what you mean by "pipeline", and how they can help/improve a project or workflow. What problem does this solve, and how does it solve that problem better than other solutions? Also, very minor nitpick, but your programming language icons shouldn't be in tags. They appear to be clickable, but do nothing, which gives the appearance that…
I think we have answered those questions on our github readme page (https://github.com/gaia-pipeline/gaia) but somehow missed that on our webpage. We will work on that!
Edit: Oh and thanks. I will fix the links of the language icons. :-)
So, a task/process queue? Is that what this is? How does this vary from the quite mature task/process queues used by media production companies? (Examples include Deadline, and dozens of tested-by-production proprietary queues at every production studio.)
I usually compare Gaia with tools like Jenkins and Spinnaker. For example, many people use Jenkins Pipeline (https://jenkins.io/solutions/pipeline/) which allows you to write CI/CD tasks in Groovy. In my opinion, Gaia fulfills this job way better because it doesn't force you to use a specific language. It's also super fast and provides features like the automatic (re)build of your pipelines.
Is there an example video somewhere on how this looks in usage?
Hey simplify. Yes, actually when you open the website ( https://gaia-pipeline.io ) it should automatically start the video. Otherwise, have a look here: https://gaia-pipeline.io/video/gaia.mp4
I’m curious what differences/trade offs there are in Gaia vs something like Argo (https://github.com/argoproj/argo) or Buildkite (https://buildkite.com/). It looks like at least one difference is an actual API for steps rather than bash commands. Is there anything interesting in terms of cross job caching (e.g. saving npm install data) or persistent runners? And obviously - what else am I not thinking about?