Any news here? It's currently some kind of a show stopper as we could not migrate to pipeline jobs...

This is a blocker for us as well.

I'm happy to try and fix this if a maintainer can point me in the right direction.

Having read over https://github.com/jenkinsci/pipeline-plugin/blob/master/DEVGUIDE.md#historical-background, I'm guessing all the references to AbstractProject/Build would need to be changed? It looks like an awful lot of code...

Ok, I think the trigger plugin actually works as of 2.29; what I was describing was done in https://issues.jenkins-ci.org/browse/JENKINS-26050. I'm able to trigger a build both blocking and nonblocking builds of a pipeline, just not as part of a multijob phase.

So, I think this can be closed, but https://issues.jenkins-ci.org/browse/JENKINS-38825 is still valid.

My environment is trigger 2.32 and jenkins 2.34, in case it's relevant.

I have no problem using freeslyle to trigger a pipeline (2.32.2)

(Currently running LTS 2.73.1) Pipeline jobs are definitely executable by the Parameterized Trigger Plugin.  However, they show as "Unresolved" in the Job page.  While that might be concerning to the Job homepage viewer, the only loss of functionality is being able to link to the job being triggered by the parent.

This is contrary to the MultiJob plugin which DOES NOT drive Pipeline jobs, period.  For the MultiJob plugin, it IS a loss of functionality.

Also, if you use Folder / Job / Branch, you can list it as such... for example, the job to trigger could be OrgScanFoo/RepoBar/BranchBaz

pipeline can be triggered, but seems it will run sequentially with the other sub-jobs in a multi-job

how can we make sure it can run parallel with the other sub-jobs?

Hello Tiejun Sha,

how did you make it happen that a pipeline job gets triggered?

I have a MultiJob, but it does not launch any sub job of type pipeline.

Would appreciate any help. In my case it can be run sequentially.

Thanks,

Hermann