-
Bug
-
Resolution: Unresolved
-
Critical
-
CentOS6, Jenkins v1.595
After upgrading to 1.595 we have noticed that if a job has a lot of builds in the queue (waiting for executors) we see 2 issues.
1. The scroll bar keeps getting reset to to the top
2. The page becomes slow/unresponsive making it difficult to use.
This might be related to JENKINS-26445
- is related to
-
-
- Resolved
-
[JENKINS-26571] Job page becomes un responsive when there are a lot of builds in the queue
Arpit Gupta
created issue -
Arpit Gupta
made changes -
| Link |
New:
This issue is related to |
Arpit Gupta
added a comment - Attaching a screenshot. Will try to create a video next time we have a lot of jobs in the queue.
Arpit Gupta
added a comment - Attaching a screenshot. Will try to create a video next time we have a lot of jobs in the queue. Arpit Gupta
made changes -
| Attachment | New: returnedScrollBAr.png [ 28416 ] |
Arpit Gupta
added a comment - Actually this is on the job page itself. Does not have to be in build now state.
Arpit Gupta
added a comment - Actually this is on the job page itself. Does not have to be in build now state. Arpit Gupta
made changes -
| Description |
Original:
After upgrading to 1.595 we have noticed that if a job has a lot of builds in the queue (waiting for executors) and the user clicks the build now button we 2 issues. 1. The scroll bar keeps getting reset to to the top 2. The page becomes slow/unresponsive making it difficult to use. This might be related to |
New:
After upgrading to 1.595 we have noticed that if a job has a lot of builds in the queue (waiting for executors) we see 2 issues. 1. The scroll bar keeps getting reset to to the top 2. The page becomes slow/unresponsive making it difficult to use. This might be related to |
| Summary | Original: Build now page becomes un responsive when there are a lot of builds in the queue | New: Job page becomes un responsive when there are a lot of builds in the queue |
We recently moved the parameters into a tool tip for JENKINS-22311. This will be in 1.598. This should at least lessen the impact.
Arpit Gupta
added a comment - Yes looks like one of the engineers tried a build with the above bug fixed and it moved past this issue. I can't confirm it as our jenkins has not been upgraded yet. We are waiting for JENKINS-26445 fix or planning to downgrade. So i will leave it up to dev's to determine if they want to resolve this as dup.
Arpit Gupta
added a comment - Yes looks like one of the engineers tried a build with the above bug fixed and it moved past this issue. I can't confirm it as our jenkins has not been upgraded yet. We are waiting for JENKINS-26445 fix or planning to downgrade. So i will leave it up to dev's to determine if they want to resolve this as dup. Arpit Gupta
added a comment - Upgraded to 1.598 and the older jobs are now getting cleaned up.
Arpit, can you add some screen shots for this please. Better again, if you can create a short screen recording and post a link.