Introduction: Running Dagger Pipelines on Jenkins

แชร์
ฝัง
  • เผยแพร่เมื่อ 22 ธ.ค. 2024

ความคิดเห็น • 4

  • @chrisre2751
    @chrisre2751 4 หลายเดือนก่อน

    Thank you. Very interesting.
    I would like to see how can I pass parameters from a result of a previous stage to another.
    Maybe in one stage I would like to grep informations from a Jira ticket and in the next stage I like tobwork with them.

    • @levlaz88
      @levlaz88 4 หลายเดือนก่อน +1

      Great question!
      There are a few ways to approach this. If you are taking the approach where you use Dagger to programatically express your pipeline, then this becomes simple because you have a variable hold the value of the JIRA API response that you pass along into another function that knows what to do with that value.
      If you want to split this up by Jenkins stage, it becomes a bit trickier but still possible through file artifacts for example.
      Please join us in Discord if you have any follow up questions, we've got a great community of folks that are exploring Dagger for various use cases and would love to see you there. discord.com/invite/dagger-io

  • @chrisre2751
    @chrisre2751 4 หลายเดือนก่อน

    Is it posible to interact and give some inpute to the pipeline on the run?
    For example I execute a terraform validate ,then pipeline should pause and I manualy check the tf changes. If everything is fine I like to resume the build and execute a terraform apply

    • @levlaz88
      @levlaz88 4 หลายเดือนก่อน +1

      There is no first-class way to pause a Dagger pipeline this way (yet!), but this is where it starts to play really nicely with Jenkins stages.
      For example you could use the input step to pause and wait for input www.jenkins.io/doc/pipeline/steps/pipeline-input-step/