https://dagger.cloud alpha - feedback welcome

[gerhard]

If you used https://dagger.cloud with dagger let us know what worked well and what you wish was better. All & any feedback welcome!

If you are curious to learn more about how Dagger Cloud makes debugging dagger issues easier, this doc page explains how to get started: Debugging with Dagger Cloud.

---

@mircubed @marcosnils please edit this as you see fit (maybe starting with this comment). I just needed a link to use in https://github.com/dagger/dagger/blame/main/docs/includes/_dagger-cloud-cta.md#L5 (part of #2763).

[gerhard]

I was using Dagger Cloud yesterday and noticed a few issues:

• run doesn't finish: https://dagger.cloud/runs/e15a94ac-51ec-4aa3-a638-ffc44369978c
• no plan showing if it fails to evaluate: https://dagger.cloud/runs/07e56777-ef54-4dfe-8360-768434140284 (there are a few others, like this one https://dagger.cloud/runs/58ad0726-19b9-4d1f-9893-04f533b61ce2)
• long run commands are not easy to read (line wrap): https://dagger.cloud/runs/4d827557-f493-4d71-a8a5-2fabd867b4a6
• CUE plan coloring after rm -rf cue.mod/pkg/* stops working properly: https://dagger.cloud/runs/4d827557-f493-4d71-a8a5-2fabd867b4a6
• showing logs in full-screen, similar to how Papertrail used to do it, would make it easier to see what is happening here: https://dagger.cloud/runs/c5ab9457-d7c3-4bc9-b2d3-869966b41cef

Happy to share more context. cc @marcosnils @mircubed @slumbering

[marcosnils]

I was using Dagger Cloud yesterday and noticed a few issues:

Looking at your runs, seems like you're using an outdated devel dagger version: https://github.com/dagger/dagger/commit/0c669c58c

Mind bumping to the latest release and trying again please? 🙏

[marcosnils]

• long run commands are not easy to read (line wrap): https://dagger.cloud/runs/4d827557-f493-4d71-a8a5-2fabd867b4a6

cc @slumbering UI feedback

• CUE plan coloring after rm -rf cue.mod/pkg/* stops working properly: https://dagger.cloud/runs/4d827557-f493-4d71-a8a5-2fabd867b4a6

yes, this is because there's no current JS cue highlighter. We have discussed about this and we're looking for alternatives.

• showing logs in full-screen, similar to how Papertrail used to do it, would make it easier to see what is happening here: https://dagger.cloud/runs/c5ab9457-d7c3-4bc9-b2d3-869966b41cef

Yep, @slumbering wanted to do some improvements here as well.

[TriplEight]

I've skimmed the doc. There's no info about how to register a (self hosted) runner, how to host a dagger UI (cloud) in case I want to have it self hosted. How does it load-balance multiple jobs between the runners. How to configure the runners. No word about any integration with k8s.
Basically, right now it doesn't seem any different from running images in any CI system.

[luolong]

Thanks @shykes and @marcosnils for your replies.

There are few concepts that I feel confusion around.
I think I understand on the higher level what is the difference between build tool and a CI pipeline, but more practical considerations here are what I am struggling with.

For example, I can see how dagger api and (and CUE pipeline definitions) help me build the pipeline and run it locally.
What remains a mystery to me is how this ties in with an actual CI/CD scenario.

I could see how I can essentially craft a CI/CD pipeline in GitLab that executes various stages of the pipeline in various pipeline staps in GitLab, but it doesn't seem to free me from having to maintain GitLab pipeline manifest in addition to Dagger manifest.

And if I re-work the pipeline in Dagger, I would always have to re-work the GitLab pipeline in parallel. Or is there some magic going on at the Dagger "CI Engine" level, that frees me from having to maintain separate GitLab maping to Dagger pipeline?

[shykes]

@luolong yes you do need to maintain a Gitlab manifest in parallel: but that manifest will be much smaller: just enough to run dagger from the right triggers. It also changes much less frequently, since the actual logic is all in your dagger code.

Most of the trouble from using a proprietary CI platform is not the occasional writing of a YAML manifest: it’s the continuous development and testing of complex pipeline logic in YAML. Moving the logic to dagger, while keeping a simple static configuration in Gitlab, is a good separation of concerns.

Down the road you could also bypass the yaml phase entirely, and run dagger from a webhook or git server hook; depending on the capabilities of your git hosting provider.

[luolong]

Okay, so, theoretically speaking, CI platforms that allow dynamic generation of pipeline manifests (Like Drone CI or Buildkite for example), could be made to generate entire pipeline manifest on the fly.

Of course, there are pipelines that have different sets of steps based on the trigger type and other attributes, but that is probably whole another can of worms there...

[shykes]

Okay, so, theoretically speaking, CI platforms that allow dynamic generation of pipeline manifests (Like Drone CI or Buildkite for example), could be made to generate entire pipeline manifest on the fly.

Of course, there are pipelines that have different sets of steps based on the trigger type and other attributes, but that is probably whole another can of worms there...

Sorry, I don't understand what you mean by the above. Does this change your understanding of how Dagger can integrate in your CI runner?

[luolong]

Does this change your understanding of how Dagger can integrate in your CI runner?

No, it dopes not change my understanding. But it does confirm my assumptions.

Sorry, I don't understand what you mean by the above

So, there exist CI tools (Buildkite and Drone CI/Woodpecker CI that I know of) that allow generating pipelines (or their DAG's) on demand for each pipeline run.

I was simply wondering if Dagger could be used at the pipeline generation phase to more closely match the Dagger specification that is being run. That would allow avoid the necessity of manually keeping the CI platform manifests in sync with Dagger definitions. Just a thought.

[sebasjm]

Can't use dagger login from server

10:18AM INFO  system | logging into your dagger account
10:18AM INFO  system | opening https://auth.dagger.cloud/authorize?....
10:18AM FATAL system | login failed: exec: "xdg-open,x-www-browser,www-browser": executable file not found in $PATH

[marcosnils]

thx for the feedback @sebasjm. Expect some updates about this really soon 🙌