Native Dagger Pipeline Engine

[olive zinc]

Hey there, Dagger is a really cool project. I have been evaluating it the past couple days and am curious if Dagger has any plans to actually replace the runners/engines that execute it. For example, replace GitHub Actions, Tekton, etc. entirely. My understanding is that this is out of scope at least for now, but I am really asking if this is planned for the future because that would make me completely sold on it. The idea of a portable CI runner is the dream (kinda like Tekton but without requiring K8s)

I did read similar content such as https://github.com/dagger/dagger/issues/4414 and #general message but this is still a bit unclear to me

[formal meadow]

Hey there! if there's enough demand I'd say that it's very likely to happen. We've spoken about this with the community and internally with the team and there's definitely a need there. Having said that, building a very lightweight component that receives the VCS (Github, Gitlab, etc) webhook call and runs some pipelines is quite trivial. We're actually prototyping something with @astral sequoia that we'll be very likely showing in the community call two weeks from now 🙌

[olive zinc]

Well that's awesome! Thanks for the update @formal meadow I'll track 🙂

[formal meadow]

We've managed to finish a prototype about this. Stay tuned to our next community call 🙏

[tawdry sage]

To be clear, Dagger currently has no plan to build our own CI runners. We prefer to complement existing CI platforms. But, we've made sure the community can easily build a new generation of Dagger-natural CI runners, if they wish to. We think that is a fantastic use case (although not for everyone), and will gladly support it. We hope to see many competing implementations in the future, and will gladly support them all. The webhook experiment by @formal meadow and @astral sequoia is a perfect example of this.

[olive zinc]

@tawdry sage thank you for clarifying! I will look for an alternative to Dagger.