#Need help with integrating dagger with azure devops cicd
1 messages · Page 1 of 1 (latest)
hey there! simplicity comes from the fact that you can express these pipelines as code. Depending on how complex and entangled your YAMLs currently are we've found that code gives you better primitives to express this logic while also benefiting from all the goodness of using an actual language like type safety, composition, reusability, testing, etc.
regarding efficiency, Dagger is a DAG based workflow system which optimizes for maximum caching. This means that based on your pipeline definition, it'll automatically run as much as it can in parallel while also keeping a cache so things that might require to be re-used across your workflow can be automatically pulled from there.
LMK if there's any specific question you'd like more information about
Having said that I'd suggest going through our quickstart here https://docs.dagger.io/quickstart/ci to give you a better idea of what I mentioned above works