#Local development not working
1 messages · Page 1 of 1 (latest)
hey @amber elbow not sure I understand if what you're asking is how to set traces locally in your machine or in Github / Gitlab
if you want to visualize your local runs, calling dagger login should be enough
I want to be able to run my CI/CD pipeline or Workflow locally so that I can debug them.
I get a success when I execute the given command, but nothing else appears...
you should be able to see your traces now in Dagger Cloud
if you go to the local tab
Yes, I finally have a "logs" appears ! Thanks a lot for the information ! Why isn't this information shown in the documentation?
Is it possible to run pipelines / workflows from local where we can just view?
seems like a miss from our side. Opening an issue to address this. cc @pulsar raptor
not sure I follow Gregory 🤔
What is the issue? We've recently introduced dagger login as a simplified way for users to send local traces to cloud. Docs need an update here https://docs.dagger.io/manuals/user/cloud-get-sta...
I'd like to know if it's possible for Dagger local to run Gitlab pipelines and Github Actions workflows like Dagger CI does.
Oh! I think there's a misunderstanding here. Dagger doesn't run Gitlab or Github pipelines locally. What Dagger enables si for you to write your pipelines in your preferred language and then run them in Github actions or Gitlab CI the same way by calling dagger call
So that I can debug the pipeline or workflow directly from my workstation without having to push the pipeline/workflow.
Seems like we need to better clarify our docs. As I mentioned above, Dagger doesn't "emulate" Gitlab CI or Github actions. The idea is that you can refactor all that YAML into actual code that you can then run locally and anywhere
Thanks a lot for all informations 🙂 I'm continuing my learning on Dagger !