• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • None
    • Jenkins ver. 2.25, Parameterized Trigger plugin 2.32

      Freestyle and Multijob projects can't trigger/call pipeline projects. When configuring the project it can see the pipeline project but upon saving it can't resolve it. For Freestyle projects it will say that the pipeline project can't be resolved. For Multijob projects it simply won't show up. And when either type is built the target pipeline job doesn't get triggered.

          [JENKINS-38998] Cannot trigger pipeline job

          Simon Weber added a comment -

          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.

          Simon Weber added a comment - 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.

          Simon Weber added a comment -

          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...

          Simon Weber added a comment - 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...

          Simon Weber added a comment -

          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.

          Simon Weber added a comment - 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.

          dan tran added a comment -

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

          dan tran added a comment - I have no problem using freeslyle to trigger a pipeline (2.32.2)

          Jeff G added a comment -

          (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

          Jeff G added a comment - (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

          Tiejun Sha added a comment -

          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?

          Tiejun Sha added a comment - 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

          Hermann Wilmsen added a comment - 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

          Tiejun Sha added a comment -

          hermannwilmsen

          1) go to /configure  for the job

          2) for Build section, you can add a build step as "Trigger/call builds on other projects"

          3) choose the pipeline job as "projects to build"

          4) you can decide whether your job will wait the result for the pipeline or not

           

          Tiejun Sha added a comment - hermannwilmsen 1) go to /configure  for the job 2) for Build section, you can add a build step as "Trigger/call builds on other projects" 3) choose the pipeline job as "projects to build" 4) you can decide whether your job will wait the result for the pipeline or not  

          Jeff G added a comment -

          freemail165 that won't work in a MultiJob Phase unfortunately.  it definitely works as a single build step, though.

          Jeff G added a comment - freemail165 that won't work in a MultiJob Phase unfortunately.  it definitely works as a single build step, though.

          Tiejun Sha added a comment -

          yes, that is what I said as " it will run sequentially with the other sub-jobs in a multi-job"

          Tiejun Sha added a comment - yes, that is what I said as " it will run sequentially with the other sub-jobs in a multi-job"

            huybrechts huybrechts
            stephencavender Stephen Cavender
            Votes:
            8 Vote for this issue
            Watchers:
            13 Start watching this issue

              Created:
              Updated: