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 created issue -
          Gosha Frost made changes -
          Labels New: plugin

          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.
          Gosha Frost made changes -
          Component/s Original: conditional-buildstep [ 15947 ]
          Gosha Frost made changes -
          Summary Original: Sub-projects that defined in conditional steps appeared as "Static" and "Other executed recently" at job main page New: Sub-projects appeared as "Static" and "Other executed recently" at job main page
          Gosha Frost made changes -
          Priority Original: Minor [ 4 ] New: Major [ 3 ]

          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
          Gosha Frost made changes -
          Assignee Original: Dominik Bartholdi [ domi ] New: huybrechts [ huybrechts ]

          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

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

              Created:
              Updated: