Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-40631

first build fails because of missing parameter

XMLWordPrintable

      The first automatic job execution of a job created by a "multibranch project" will be triggered without parameters. e.g. the following pipeline will print "null" instead of the default value of MY_PARAM. Subsequent executions will work correctly. This is very unfortunate, as such jobs are typically created for short lived branches, in the most ideal case, no further commits are even made to them - they get merged and vanish again.

      pipeline {

  parameters {
    choiceParam(choices: 'AA\nBB', description: 'please select...', name: 'MY_PARAM')
  }  

  agent any
  stages {

    stage ('test') {
      steps {
          sh "echo ${env.MY_PARAM}"
      }
    }
  }
}

          [JENKINS-40631] first build fails because of missing parameter

          Andrew Bayer added a comment -

          Try params.PARAM - I think that'll work.

          Andrew Bayer added a comment - Try params.PARAM - I think that'll work.

          Dominik Bartholdi added a comment -

          many thanks, that works!! I try to take some time to enhance the documentation...

          Dominik Bartholdi added a comment - many thanks, that works!! I try to take some time to enhance the documentation...

          Liam Newman added a comment -

          Bulk closing resolved issues.

          Liam Newman added a comment - Bulk closing resolved issues.

            abayer Andrew Bayer
            imod Dominik Bartholdi
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: