Dagger in Buildkite CI

[vernal fog]

Hi Iano! Yes, your question makes sense. At the moment, Dagger itself does not handle event triggers, and does not handle dispatching jobs across several machines. Typically you would continue relying on your CI infrastructure for that (in your case, Buildkite), and configure Buildkite jobs that run the desired Dagger pipeline.

So if you want to configure job parallelism (which jobs run on which machines), you should configure that in Buildkite

We do plan on adding event triggers, and multi-machine scheduling eventually. So it will be possible eventually to build your entire CI stack on top of Dagger, if you want. But for now, piggybacking on your existing CI infrastructure allows us to focus our engineering effort on the most differentiating part of Dagger: the DAG engine, caching and developer experience

[spring bay]

is there any timeline on enabling that?

I would like to not make people write yaml if at all possible 🙂

[vernal fog]

Probably not until next year. But typically what happens, is that you write very little yaml, and it almost never changes

You configure the CI infrastructure once, with a small amount of yaml (just enough to run dagger)