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

View - Filter Build Executors always filters based on the default view

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Minor Minor
    • core
    • None

      Background:
      We recently upgraded from 1.503 to 1.538
      We had a six views. Each view has 5 to 30 projects. The views have:

      • "filter build queue" = true
      • "filter build executors" = true
      • "Use a regular expression to include jobs into the view" = true
      • a few random jobs are selected as well from the overall list

      Issue:
      the executors are getting filtered out properly when you look at the view for 5 seconds. after the 5 seconds it seems like an AJAX poll kicks off and then the executors are filtered out based on a different view's settings.

      All views are filtered to the same view and it is whatever the default view is set to.

          [JENKINS-20548] View - Filter Build Executors always filters based on the default view

          clint axeda created issue -

          clint axeda added a comment -

          this might be a dupe of https://issues.jenkins-ci.org/browse/JENKINS-20500 which has no action on it. As that bug states - when AUTO REFRESH is enabled - this issue does not seem to happen. I didn't find it when searching because the way we characterize the bug was different. I think this bug describes the problem more accurately because it's not that it's not filtered - it's that it's filtered to whatever the 'default view' is configured to be.

          clint axeda added a comment - this might be a dupe of https://issues.jenkins-ci.org/browse/JENKINS-20500 which has no action on it. As that bug states - when AUTO REFRESH is enabled - this issue does not seem to happen. I didn't find it when searching because the way we characterize the bug was different. I think this bug describes the problem more accurately because it's not that it's not filtered - it's that it's filtered to whatever the 'default view' is configured to be.

          > I think this bug describes the problem more accurately.

          It's correct. I've found the cause of the problem.
          I'll send a pull request.

          Thanks,

          Yoichi Nakayama added a comment - > I think this bug describes the problem more accurately. It's correct. I've found the cause of the problem. I'll send a pull request. Thanks,
          Yoichi Nakayama made changes -
          Link New: This issue duplicates JENKINS-20500 [ JENKINS-20500 ]

          clint axeda added a comment -

          any chance we can get this taken care of? it's not critical but it is a terrible nuisance for anyone with multiple views and filtered executors...

          clint axeda added a comment - any chance we can get this taken care of? it's not critical but it is a terrible nuisance for anyone with multiple views and filtered executors...

          clint axeda added a comment -

          i don't know if bumping this is a bad idea. i don't want to annoy peeps with this. anybody have clue how we can get this on the radar?

          clint axeda added a comment - i don't know if bumping this is a bad idea. i don't want to annoy peeps with this. anybody have clue how we can get this on the radar?
          Jesse Glick made changes -
          Resolution New: Duplicate [ 3 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

          clint axeda added a comment -

          anybody even lookin at this bug?

          clint axeda added a comment - anybody even lookin at this bug?

          Richard Otter added a comment - - edited

          Yes, please fix. I just spent about 90 min troubleshooting this until I found this report.

          Richard Otter added a comment - - edited Yes, please fix. I just spent about 90 min troubleshooting this until I found this report.

          dlavelle added a comment -

          Any reason why this fix didnt make it into the 1.532.2 LTS release? it was dropped well after this bug was reported.

          dlavelle added a comment - Any reason why this fix didnt make it into the 1.532.2 LTS release? it was dropped well after this bug was reported.

            Unassigned Unassigned
            axeda_clint clint axeda
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: