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

Build queue is not filtered after progress updated

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

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

        Attachments

          Issue Links

            Activity

            Hide
            danielbeck Daniel Beck added a comment -

            It was missed because the fix isn't even merged to regular releases, so isn't eligible for inclusion in LTS.

            Show
            danielbeck Daniel Beck added a comment - It was missed because the fix isn't even merged to regular releases, so isn't eligible for inclusion in LTS.
            Hide
            axeda_clint clint axeda added a comment -

            i definitely voted for it. we have many executors, many views - this bug is really painful for us

            Show
            axeda_clint clint axeda added a comment - i definitely voted for it. we have many executors, many views - this bug is really painful for us
            Hide
            scm_issue_link SCM/JIRA link daemon added a comment -

            Code changed in jenkins
            User: Jesse Glick
            Path:
            changelog.html
            core/src/main/resources/jenkins/widgets/BuildQueueWidget/index.groovy
            core/src/main/resources/jenkins/widgets/ExecutorsWidget/index.groovy
            http://jenkins-ci.org/commit/jenkins/20ea8d1092f5642cc889d80f7c2f7d3334e3739e
            Log:
            [FIXED JENKINS-20500] Pass ${it} as an alias for ${view} to t:queue and t:executors, correcting regression introduced in 8e6a3f7.

            Show
            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/resources/jenkins/widgets/BuildQueueWidget/index.groovy core/src/main/resources/jenkins/widgets/ExecutorsWidget/index.groovy http://jenkins-ci.org/commit/jenkins/20ea8d1092f5642cc889d80f7c2f7d3334e3739e Log: [FIXED JENKINS-20500] Pass ${it} as an alias for ${view} to t:queue and t:executors, correcting regression introduced in 8e6a3f7.
            Hide
            dogfood dogfood added a comment -

            Integrated in jenkins_main_trunk #3259
            [FIXED JENKINS-20500] Pass ${it} as an alias for ${view} to t:queue and t:executors, correcting regression introduced in 8e6a3f7. (Revision 20ea8d1092f5642cc889d80f7c2f7d3334e3739e)

            Result = SUCCESS
            Jesse Glick : 20ea8d1092f5642cc889d80f7c2f7d3334e3739e
            Files :

            • core/src/main/resources/jenkins/widgets/BuildQueueWidget/index.groovy
            • core/src/main/resources/jenkins/widgets/ExecutorsWidget/index.groovy
            • changelog.html
            Show
            dogfood dogfood added a comment - Integrated in jenkins_main_trunk #3259 [FIXED JENKINS-20500] Pass ${it} as an alias for ${view} to t:queue and t:executors, correcting regression introduced in 8e6a3f7. (Revision 20ea8d1092f5642cc889d80f7c2f7d3334e3739e) Result = SUCCESS Jesse Glick : 20ea8d1092f5642cc889d80f7c2f7d3334e3739e Files : core/src/main/resources/jenkins/widgets/BuildQueueWidget/index.groovy core/src/main/resources/jenkins/widgets/ExecutorsWidget/index.groovy changelog.html
            Hide
            leedega Kevin Phillips added a comment - - edited

            As was mentioned previously, we too are experiencing this same problem in the latest LTS edition 1.532.3. Ironically we were not experiencing this problem prior to upgrading from 1.509.2 so whatever is causing this issue was introduced in an update to the LTS edition, so it seems odd an LTS fix would not be equally relevant.

            Show
            leedega Kevin Phillips added a comment - - edited As was mentioned previously, we too are experiencing this same problem in the latest LTS edition 1.532.3. Ironically we were not experiencing this problem prior to upgrading from 1.509.2 so whatever is causing this issue was introduced in an update to the LTS edition, so it seems odd an LTS fix would not be equally relevant.

              People

              • Assignee:
                jglick Jesse Glick
                Reporter:
                yoichi Yoichi Nakayama
              • Votes:
                3 Vote for this issue
                Watchers:
                11 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: