#if a company is using a combination of

1 messages · Page 1 of 1 (latest)

mossy shale
#

Today Dagger mostly solves the pipeline definition and execution problem, but there are still things that the CI system does (like listen for webhooks) that Dagger does not do (yet!)

Dagger pipelines run anywhere, so its a way to standardize on dagger and then keep all of your existing CI systems, it allows them to play nicely together.

novel spruce
#

This 👆

I think the natural transition would be:

Before Dagger:

  • Github Actions on k8s
  • Jenkins on k8s
  • Ad-hoc automation on dev machines
  • Spinnaker

After Dagger:

  • Dagger on GHA/k8s
  • Dagger on Jenkins/k8s
  • Dagger on dev machines
  • Spinnaker

Explanation:

  • Pipeline logic can be shared between GHA, Jenkins, and local dev machines. This makes CI more productive and efficient overall
  • GHA and Jenkins configurations become simpler: they gradually become infrastructure for dispatching events and machines to the dagger pipelines
  • Spinnaker continues to run the same. You integrate into it from Dagger, the same way you would from GHA or Jenkins, but with portable code.
broken birch
#

thank you @sol and @mossy shale for your responses , these will help me make a case to use dagger in our cicd systems