News for hackers. Stuff that matters.
Re:Dagger Python SDK: Develop Your CI/CD Pipelines as Code by JackMcMack on Thursday November 10, 2022 @05:12PM (#33554256)
The 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.

Re:Dagger Python SDK: Develop Your CI/CD Pipelines as Code by shykes on Thursday November 10, 2022 @06:33PM (#33555207)
> 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 :)

Re:Dagger Python SDK: Develop Your CI/CD Pipelines as Code by senorsmile on Thursday November 10, 2022 @11:31PM (#33557331)
What 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.
Re:Dagger Python SDK: Develop Your CI/CD Pipelines as Code by shykes on Friday November 11, 2022 @12:03AM (#33557478)
I 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?