Is there a way to tell dagger to ignore | Dagger | Page 1

crisp viper May 24, 2024, 3:45 PM

#

@scenic cloak @fair hazel and some of us were discussing how to make this a better experience yesterday.

fair hazel May 24, 2024, 3:52 PM

#

Doesn't just --my-arg "" do what you need?

dim pagoda May 24, 2024, 3:56 PM

#

hmm I didn't try ""... if you are familiar with Jenkins, I directly used the input parameter like --my-arg $params.myArg and kept the parameter field blank. That effectively becomes --my-arg . If I wanted to add "" I'm afraid I'd have to add a condition.

crisp viper May 24, 2024, 3:57 PM

#

@dim pagoda ah, okay, I was also going to ask if you're just using // +optional or also using // +default at all in your cases.

#

Do you use declarative pipelines or scripted pipelines?

dim pagoda May 24, 2024, 4:02 PM

#

declarative, I tried both ways. having just // +optional and with // +default

fair hazel May 24, 2024, 4:03 PM

#

What about --my-arg "$params.myArg"? Doesn't that work?

#

Good to do it like that anyway to prevent values from variables having spaces inside.

dim pagoda May 24, 2024, 4:04 PM

#

good point, let me try that

#

ok that worked. I feel silly for not trying that

crisp viper May 24, 2024, 4:14 PM

#

I was wondering if something like this would be needed.

pipeline {
    agent any
    
    stages {
        stage('Example Stage') {
            steps {
                sh dagger call foo --my-arg "${params.myArg}"
            }
        }
    }
}

Nice! Glad to learn that this works! (note real one below 👇 )

dim pagoda May 24, 2024, 4:16 PM

#

This is what I did

sh "dagger call -m ./mymodule promote --sources \"$params.sources\" --user PIPELINE_USR --pass PIPELINE_PSW --tag \"$params.tag\" --targetTag \"$params.targetTag\""

#Is there a way to tell dagger to ignore