Dagger in Action: Restoring Developer Confidence in CI
Read more

CI/CD as Code that Runs Anywhere

import { connect, Client } from "@dagger.io/dagger"

connect(async (client: Client) => {
  const ctr = client
    .pipeline("test")
    .container()
    .from("alpine")
    .withExec(["apk", "add", "curl"])
    .withExec(["curl", "https://dagger.io"])

  const result = await ctr.stdout()

  console.log(result.substring(0, 300))
})
Daggernaut
Conor Barber
Conor BarberAirbyte
Before Dagger it was 'Push and Pray.' Now, we have the same tool running locally and in CI, and that just streamlines everything. Now our mantra is test, test, test, test.
Tony Worm
Tony Wormhof - the high code framework
With Dagger, I can define what I want my desired results to be, and Dagger figures out what needs to happen to get those results.
Andy Gonzalez
Andy GonzalezFortune 500 company
Replacing our makefiles with Dagger has greatly simplified our process for deployments since itโ€™s much faster (1-3 hours to 3 minutes)...The power, flexibility and capability behind Dagger is something that gets me excited.
James Qualls
James QuallsDiscern
We want to be able to ship every single day, multiple times a day, as fast as we possibly can. Dagger is enabling us to do that.
Kevin Minehart
Kevin MinehartGrafana
With Dagger, we were able to go from something that takes an hour to something that takes 8 minutes.
George MacRorie
George MacRorieFlipt
Dagger feels like an actual innovation in CI/CD. There's a real attention to getting feedback from everyone and feeding that back into the design and building something that people need.

Get involved with the community! ๐Ÿš€

Join the conversation on Discord & GitHub, and help shape the evolution of Dagger.

community