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

Subprojects appeared as "Unresolved" if the "projects to build" is a pipeline job.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • parameterized-trigger-plugin
    • None
    • Jenkins 2.19.1
      parameterized-trigger-plugin2.32

      Scenario: The job A launches job B by configuring "projects to build", and B is a pipeline job.
      Issue: Main page of job A shows:
      Subprojects
      Unresolved
      B

          [JENKINS-41194] Subprojects appeared as "Unresolved" if the "projects to build" is a pipeline job.

          Ning Wang created issue -

          Peter Han added a comment -

          On Jenkins 1.596.1, old fashion pipeline - workflow job has the same issue.

          Peter Han added a comment - On Jenkins 1.596.1, old fashion pipeline - workflow job has the same issue.

          Gavin Hurlbut added a comment -

          I am seeing the same issue on 2.19.4 with a parameterized pipeline job as the subproject.

          Gavin Hurlbut added a comment - I am seeing the same issue on 2.19.4 with a parameterized pipeline job as the subproject.

          Jason Davis added a comment - - edited

          Additionally - if the triggered pipeline job is configured as a Post Build action (trigger parameterized build on other projects), the pipeline job doesn't appear at all as a "Downstream Project" on the project page.  

          Jason Davis added a comment - - edited Additionally - if the triggered pipeline job is configured as a Post Build action (trigger parameterized build on other projects), the pipeline job doesn't appear at all as a "Downstream Project" on the project page.  

          Doron Shai added a comment - - edited

          Also relevant with Plugin version 2.35.1 and Jenkins version 2.41

          In addition: When I add a freestyle project and after few builds I remove it, still I see the old freestyle job as a sub-project.

          Doron Shai added a comment - - edited Also relevant with Plugin version 2.35.1 and Jenkins version  2.41 In addition: When I add a freestyle project and after few builds I remove it, still I see the old freestyle job as a sub-project.

          Ivan Dragomilov added a comment -

          Jenkins 2.92 + plugin 2.35.1, bug exists

          Ivan Dragomilov added a comment - Jenkins 2.92 + plugin 2.35.1, bug exists

          Moe Hussein added a comment -

          LTS  2.89.3 + 2.35.2  bug exists as well.

          Moe Hussein added a comment - LTS  2.89.3 + 2.35.2  bug exists as well.

          Simon Weber added a comment -

          Here's a potential fix to try out: https://github.com/jenkinsci/parameterized-trigger-plugin/compare/master...venmo:resolve_pipelines. ymmv; I mostly just copied the approach from https://issues.jenkins-ci.org/browse/JENKINS-38825.

          Simon Weber added a comment - Here's a potential fix to try out: https://github.com/jenkinsci/parameterized-trigger-plugin/compare/master...venmo:resolve_pipelines . ymmv; I mostly just copied the approach from https://issues.jenkins-ci.org/browse/JENKINS-38825 .

          Neil Calverley added a comment -

          Just ran into this bug as well

          LTS 2.107.3 + 2.35.2

          Neil Calverley added a comment - Just ran into this bug as well LTS 2.107.3 + 2.35.2
          Dmitriy Korovkin made changes -
          Priority Original: Major [ 3 ] New: Critical [ 2 ]

            huybrechts huybrechts
            ningwang Ning Wang
            Votes:
            22 Vote for this issue
            Watchers:
            20 Start watching this issue

              Created:
              Updated: