Dagger: a new way to build CI/CD pipelines

Re:Dagger: a new way to build CI/CD pipelines by ______-_-______ on Wednesday March 30, 2022 @06:55PM (#30861866)

I assume if the jenkins-step failed, you'd click a link to the dagger UI to see which dagger-step failed. Alternatively, never open jenkins at all and instead keep a tab open with the dagger UI.

[ Parent | on HN ]

Re:Dagger: a new way to build CI/CD pipelines by shykes on Wednesday March 30, 2022 @09:24PM (#30862852)

Yes, that’s right. Especially since you’re probably running the same dagger actions all day long in development, upstream from CI.

[ Parent | on HN ]

Re:Dagger: a new way to build CI/CD pipelines by chologrande on Thursday March 31, 2022 @01:34AM (#30864134)

I guess I'm a little confused where the line here...

Where is dagger UI and how does it relate to your CI? I don't see it in docs or cli help. Sounds like Dagger UI in this context (above) is providing little value beyond logging if it's not doing workflow execution.

I ask not to talk down on the product, but because I'm actually quite interested. Local execution, plus containerized execution sounds awesome. Just trying to understand the vision.

[ Parent | on HN ]