#I've been rewriting some of my older,

1 messages · Page 1 of 1 (latest)

brave trench
#

Hi!

Not having to think about calling Pipeline at the right place and time removed so much of the mental overhead of creating new Dagger pipelines.

That's so great to hear. I've been wondering whether we carry .pipeline forward or not. I hoped modules and their functions would give everyone a better UX - from authoring pipelines to visualizing them.

For visualization, we are working on adding support for modules into the Dagger Cloud UI. I'll message you to get your input on the UX.

#

cc @low solstice @chrome widget @delicate vortex ^^

latent falcon
#

I like the idea of being able to provide my own grouping (separate different module calls into logical steps, so I can get to the part I’m interested in quickly), but using pipeline is quite taxing (at least in Go). :/
Not sure what would work better.

#

Per module grouping is a good start I guess