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

When the build queue has a number of jobs in it, they are briefly displayed and then they disappear. If the page is manually refreshed, then jobs will appear briefly again before the same thing occurs.

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • core
    • Windows 7
      Chrome (30.0.1599.69)
      Internet Explorer (8.0.7601.17514)

      For the view "start" the "Filter build queue" & "Filter build executors" are marked.
      For the rest of the different views these Filters are not set.
      The build queue is first displayed and after 5 seconds or with "scrolling down" it disappears.

      [Workaround]
      The AUTO REFRESH for the site was disabled. After enabling it, the problem does not appear.

      [Update]
      The error is inherited by the Main page. If you set the filter in "start" the filter applied to all other pages. But it seemed to happen only if you begin at "start" and then go to the different views.
      If you go directly to a page further down, it inherited different.

      Unchecking the filter at "start" solves the problem. But still it seem to be bug.

          [JENKINS-20252] When the build queue has a number of jobs in it, they are briefly displayed and then they disappear. If the page is manually refreshed, then jobs will appear briefly again before the same thing occurs.

          Chris Engel created issue -
          Chris Engel made changes -
          Summary Original: When the build queue has a number of job in it, they are briefly displayed and then they disappear. If the page is manually refreshed, then jobs will appear briefly again before the same thing occurs. New: When the build queue has a number of jobs in it, they are briefly displayed and then they disappear. If the page is manually refreshed, then jobs will appear briefly again before the same thing occurs.
          Chris Engel made changes -
          Labels Original: gui jenkins job New: gui jenkins job queue
          Chris Engel made changes -
          Affects Version/s New: current [ 10162 ]
          Environment Original: Chrome (30.0.1599.69)
          Internet Explorer (8.0.7601.17514)
          New: Windows 7
          Chrome (30.0.1599.69)
          Internet Explorer (8.0.7601.17514)
          Chris Engel made changes -
          Description Original: For the view "start" the "Filter build queue" & "Filter build executors" are marked.
          For the rest of the different views these Filters are not set.
          The build queue is first displayed and after 5 seconds or with "scrolling down" it disappears.

          [Workaround]
          The AUTO REFRESH for the site was disabled. After enabling it, the problem does not appear.
          New: For the view "start" the "Filter build queue" & "Filter build executors" are marked.
          For the rest of the different views these Filters are not set.
          The build queue is first displayed and after 5 seconds or with "scrolling down" it disappears.

          [Workaround]
          The AUTO REFRESH for the site was disabled. After enabling it, the problem does not appear.

          [Update]
          The error is inherited by the Main page. If you set the filter in "start" the filter applied to all other pages. But it seemed to happen only if you begin at "start" and then go to the different views.
          If you go directly to a page further down, it inherited different.

          Unchecking the filter at "start" solves the problem. But still it seem to be bug.
          Priority Original: Major [ 3 ] New: Minor [ 4 ]
          SCM/JIRA link daemon made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 151776 ] New: JNJira + In-Review [ 194089 ]

            Unassigned Unassigned
            sethosinoffice Chris Engel
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: