Hi felipecassiors,

I am having the same issue but using the above workaround didn't work. I have two parameters one of them is a choice that is populated by a list variable. The other one is an empty text field to be populated later. None of them can have a default value.

Thanks

Try with this:

stage('prepare') {
  steps {
    // Initialize params as envvars, workaround for bug https://issues.jenkins-ci.org/browse/JENKINS-41929
    script { params.each { k, v -> env[k] = "${v}" } }
  }
}

Thanks felipecassiors  for your quick reply. It didn't work too. In my case, I am using the seed job to update the Jenkins pipeline jobs. Once, I run the seed job, the "Build with Parameters" options disappears from the updated pipeline and I then am left with just "build"

It is OK for most of my jobs to just start and stop a job manually to bring the "Build with Parameters" back but the problem is with the scheduled ones. They won't start unless I manually start/stop them first.

hello jensre, what worked for me is: I get the job via API, I get the 'nextBuildNumber' field, then when I upload the jenkinsfile of a job I add to the jenkinsfile a check if the build number is equal to <nextBuildNumber> , then abort the build, this way the button is 'build with parameters' for all the upcoming builds.

Hi jensre , in your case this is easier.

In your seed job, include in your pipeline job definition the parameters:

pipelineJob('YourJob')

    parameters {stringParam('Second param')}

Then the "Build with Parameters" will be available after the seed job creates/updates your pipeline jobs.