3 ms·
Hey, lead developer for the Python SDK here. I have a few examples in https://github.com/helderco/dagger-examples https://github.com/helderco/dagger-examples a
by helderco 4y ago
Hey, lead developer for the Python SDK here.
I have a few examples in https://github.com/helderco/dagger-examples https://github.com/helderco/dagger-examples and I plan to add more.
There's also reference documentation in https://dagger-io.readthedocs.io/ https://dagger-io.readthedocs.io/ so you can get a birds eye view on what's possible.
- anentropic 4y agoHaven't tried it yet, but I like the features!
- JackMcMack 4y agoThe api looks very simple and easy, that's a very good sign. We've been doing similar stuff in python, mainly in combination with Pulumi automation. You can do some very fancy things, and I'm sure Dagger would be a nice addition to that. But honestly the thing I'm missing most is a nice UI above all that. How to present realtime and historic logs (and state) for multiple concurrent actions is still not as easy as I think it could be.
- shykes 4y ago> I'm missing most is a nice UI above all that. How to present realtime and historic logs (and state) for multiple concurrent actions is still not as easy as I think it could be. We have plans to solve that :)
- senorsmile 4y agoWhat I'd like to see is integrations with existing systems. If I could somehow automatically map stages in dagger to the stages in a Jenkins pipeline, this would be ideal.
- shykes 4y agoI agree, that would be very useful. We have been investigating the best way to deliver this. Probably a generator tool, that would take a dagger project as input, and produce a jenkins configuration as output. This of course could itself be a dagger pipeline :) Any guidelines on how to structure the final jenkins configuration? What would the stages look like in your project for example? Any mistakes to avoid?