#Hello everyone

1 messages · Page 1 of 1 (latest)

last roost
#

👋

  • As the product is still in 0.x.x, the releace frequency is relatively fast. We generally craft a release within one or two weeks so we can ship new feaures to our users and get feedback.
  • Yes, Dagger can run with kubernetes. We have a demo of that working here: #1084673886299369493 message. You'll notice it requires some configurations from the k8s side to make it work. If you prefer a more self-service option, you can DM us for more details
  • We have a comprehensive getting started self-guided interactive tutorial here: https://docs.dagger.io/648215/quickstart/
  • States, logs and cache is handled by our Dagger Engine. Is there something in particular you're interested to know about how it works?
Discord

Discord is the easiest way to communicate over voice, video, and text. Chat, hang out, and stay close with your friends and communities.

Introduction

harsh granite
#

hello, sorry for my delay, I had a lot of work!!

thank you for your answer, I'll see what I can do because I'm new to Devops, I'll have other questions if you're okay!

How are the stages of a pipeline and the results (logs, states, ...) stored? And how do you query the status of a pipeline?

Is it possible to partially restart part of the pipeline?

thank you very much

last roost
#

How are the stages of a pipeline and the results (logs, states, ...) stored? And how do you query the status of a pipeline?

By default they're not stored anywhere for the open source engine. We do have a commercial product currently that offers log retention and pipeline visiblity as well so you can check all this

#

Is it possible to partially restart part of the pipeline?

If a pipeline fails given a temporary error for example, once you run your pipeline again, it'll continue running from where it failed since all the previous steps will be automatically cached. If you need to force a restart even your pipeline succeeded in the past, you can manually do that by making a small change in your pipeline which causes that step (and all its dependents) to be re-triggered

harsh granite