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

Build queue is not filtered after progress updated

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • core
    • Jenkins 1.538

      1. check "Filter build queue" in view configuration of View-A
      2. schedule several builds for jobs not included in View-A
      3. show View-A, builds scheduled by step 2 are not appeared in "Build Queue"
      4. stay in View-A until progress updated in "Build Executor Status"
      5. all builds appear in "Build Queue"

      The problem does not occur with auto refresh by "ENABLE AUTO REFRESH".

          [JENKINS-20500] Build queue is not filtered after progress updated

          Yoichi Nakayama created issue -
          Yoichi Nakayama made changes -
          Assignee New: Yoichi Nakayama [ yoichi ]
          Yoichi Nakayama made changes -
          Link New: This issue is duplicated by JENKINS-20548 [ JENKINS-20548 ]

          Yoichi Nakayama added a comment - I've sent a pull request https://github.com/jenkinsci/jenkins/pull/1011
          Yoichi Nakayama made changes -
          Link New: This issue is related to JENKINS-18128 [ JENKINS-18128 ]
          Daniel Beck made changes -
          Labels New: lts-candidate

          Daniel Beck added a comment -

          This is a rather big issue when the build queue is at 1000+ entries.

          Daniel Beck added a comment - This is a rather big issue when the build queue is at 1000+ entries.

          clint axeda added a comment -

          it is worth noting that the bug i had filed and was closed as dupe of this bug highlights that the controlling factor here is what the 'default view' is set to. if one uses views for segregating jobs whichever view is set to the default is the one which is displayed.

          From Yoichi's pull request - it seems to be good to go. Any possibility of including this bug in the near future? pretty please?

          clint axeda added a comment - it is worth noting that the bug i had filed and was closed as dupe of this bug highlights that the controlling factor here is what the 'default view' is set to. if one uses views for segregating jobs whichever view is set to the default is the one which is displayed. From Yoichi's pull request - it seems to be good to go. Any possibility of including this bug in the near future? pretty please?

          Yoichi Nakayama added a comment - A question was sent from jglick https://github.com/jenkinsci/jenkins/commit/8e6a3f7f03c8cdd93f1fb352088bac9cd2676c49
          Yoichi Nakayama made changes -
          Assignee Original: Yoichi Nakayama [ yoichi ] New: Kohsuke Kawaguchi [ kohsuke ]

            jglick Jesse Glick
            yoichi Yoichi Nakayama
            Votes:
            3 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: