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

Sub-projects appeared as "Static" and "Other executed recently" at job main page

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • Jenkins 1.532.2
      Parameterized Trigger plugin 2.24
      conditional-buildstep 1.3.3

      Scenario: The job A launches two sub jobs B and C according to the condition steps.
      Issue: Main page of job A shows the sub-projects B and C twice as "Static" and "Other executed recently"

      In case of one sub-project the behavior is correct - only "Static" is appearing.

      See attached screenshots

        1. configure.png
          configure.png
          30 kB
        2. jobA.png
          jobA.png
          22 kB

          [JENKINS-22600] Sub-projects appeared as "Static" and "Other executed recently" at job main page

          Gosha Frost added a comment -

          Actually the sub-projects shown twice just in case of more than one of "Trigger/call builds on other projects" build steps.

          Gosha Frost added a comment - Actually the sub-projects shown twice just in case of more than one of "Trigger/call builds on other projects" build steps.

          Fred G added a comment -

          This problem is not specific to a configuration that involves the conditional buildstep plugin.
          I have the same problem without conditional buildsteps.
          Therefore Dominik is probably not the right assignee.

          Here is the commit that added this new behavior:
          https://github.com/jenkinsci/parameterized-trigger-plugin/commit/a443010853f7ec231233a1685d20671da58f6f31
          It was added by Github user "JOSivtoft". Unfortunately there seems to be no matching JIRA username.

          Fred G added a comment - This problem is not specific to a configuration that involves the conditional buildstep plugin. I have the same problem without conditional buildsteps. Therefore Dominik is probably not the right assignee. Here is the commit that added this new behavior: https://github.com/jenkinsci/parameterized-trigger-plugin/commit/a443010853f7ec231233a1685d20671da58f6f31 It was added by Github user "JOSivtoft". Unfortunately there seems to be no matching JIRA username.

          Gosha Frost added a comment -

          Re-assign to the leader of project

          Gosha Frost added a comment - Re-assign to the leader of project

          Affects only upstream jobs which are paced in the Jenkins root (https://ci.org/job/A) and trigger jobs which also paced in the Jenkins root (https://ci.org/job/B)
          As workaround I have moved all downstream jobs into folders(https://ci.org/job/QA/B) and "Other executed recently" items disappeared

          Vitalii Baskov added a comment - Affects only upstream jobs which are paced in the Jenkins root ( https://ci.org/job/A ) and trigger jobs which also paced in the Jenkins root ( https://ci.org/job/B ) As workaround I have moved all downstream jobs into folders( https://ci.org/job/QA/B ) and "Other executed recently" items disappeared

          Arun Thomas added a comment -

          The page load time increases unbearably when many downstream projects are triggered. Having multiple downstream projects creates sections of "Static" and "Other Executed Recently" that are unnecessarily duplicated. I tried what Vitaliy suggested of placing jobs in a sub-folder on our server but then the jobs do not show up.

          Arun Thomas added a comment - The page load time increases unbearably when many downstream projects are triggered. Having multiple downstream projects creates sections of "Static" and "Other Executed Recently" that are unnecessarily duplicated. I tried what Vitaliy suggested of placing jobs in a sub-folder on our server but then the jobs do not show up.

          Jeff G added a comment -

          I'm using Jenkins 1.609.3 and am also experiencing this problem. Triggering several downstream jobs from a "driver" job. A couple of the downstream jobs are a health check used by several other jobs. As a result, the driver job shows "Other executed recently" of those shared jobs several times. I am not using the conditional build step anywhere in this job.

          All of my plugins are updated to the latest monthly in my environment.

          System information.
          Master OS: Ubuntu
          Slave OS: Ubuntu/SuSe/Windows 2008

          I first observed this around a year ago and just got around to commenting on this ticket. Added to the vote.

          Jeff G added a comment - I'm using Jenkins 1.609.3 and am also experiencing this problem. Triggering several downstream jobs from a "driver" job. A couple of the downstream jobs are a health check used by several other jobs. As a result, the driver job shows "Other executed recently" of those shared jobs several times. I am not using the conditional build step anywhere in this job. All of my plugins are updated to the latest monthly in my environment. System information. Master OS: Ubuntu Slave OS: Ubuntu/SuSe/Windows 2008 I first observed this around a year ago and just got around to commenting on this ticket. Added to the vote.

          I'm at latest Jenkins LTS 1.651.1, with Parameterized Trigger plugin version 2.30, and am experiencing this issue. Am hoping someone can fix it soon.

          Rick Patterson added a comment - I'm at latest Jenkins LTS 1.651.1, with Parameterized Trigger plugin version 2.30, and am experiencing this issue. Am hoping someone can fix it soon.

          Any updates? Issue has almost 4 years and it is still not fixed. This is verry annoying issue.

          Mariusz Piliszek added a comment - Any updates? Issue has almost 4 years and it is still not fixed. This is verry annoying issue.

            cjo9900 cjo9900
            gosha_f Gosha Frost
            Votes:
            12 Vote for this issue
            Watchers:
            14 Start watching this issue

              Created:
              Updated: