Multi-configuration project ALWAYS triggers parametrized build for ALL childs if a pipeline job in the project list to build

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      Let's compare behavior of  a pipeline job and a freestyle job when they are triggered as parametrized build in the Post-Build section from a Mutli-configuration job.

      In my example I have a multi-configuration job :

      test-parametrizedPlugin-multi-conf-job that calls 2 jobs one freestyle and one pipeline :

      • test-parametrizedPlugin-called-pipeline-job
      • test-parametrizedPlugin-called-freestyle-job

       

      First test, the 2 jobs are in the same Projects to build list( Note that the Trigger build from child project option is not set ):

      Then the 2 jobs are triggered for each child as we can see as it is reported in the console logs of the 2 called jobs.

      Second test, the 2 jobs are in separate Projects to build list( Note that the Trigger build from child project option is not set ) :

      Then the 2 jobs are triggered but not with the same behavior,

      freestyle job is run as expected :

      but pipeline job is run for each child as we can see as it is reported in the console log:

            Assignee:
            Unassigned
            Reporter:
            Damien Merlin
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Archived: