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

Triggering a parametrized job from shared library sometimes deletes all parameters

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      We have a multibranch pipeline job that triggers a parametrized pipeline build by calling a method from our shared library like so:

      build job: "job-with-params", parameters: [
      [$class: 'StringParameterValue', name: 'first', value: "1"],
      [$class: 'StringParameterValue', name: 'second', value: "2"]
      ],
      wait: true,
      propagate: 
      false,
      quietPeriod: 0
      

      From time to time, all parameters of our parametrized job get deleted when running this trigger and the job ends up as a regular pipeline job without any parameters. So far we can not determine why this happens. The triggering happens from a shared library we use with the workflow-cps-global-lib plugin. Any ideas would be highly appreciated, so far we are absolutely clueless. I will update this issue once we find out more.

        Attachments

          Activity

          Hide
          jglick Jesse Glick added a comment -

          No idea what could cause such a problem, unless the downstream build is using the properties step to define its parameters and it sometimes omits that job property.

          Obviously if you find a way to reproduce, reopen with details.

          Show
          jglick Jesse Glick added a comment - No idea what could cause such a problem, unless the downstream build is using the properties step to define its parameters and it sometimes omits that job property. Obviously if you find a way to reproduce, reopen with details.
          Hide
          tobilarscheid Tobias Larscheid added a comment -

          You are absolutely right, we were using a properties step in the downstream build and did not realize that it is not adding to the parameters but actually overwriting them.

          Show
          tobilarscheid Tobias Larscheid added a comment - You are absolutely right, we were using a properties step in the downstream build and did not realize that it is not adding to the parameters but actually overwriting them.

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            tobilarscheid Tobias Larscheid
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: