Arpit, can you add some screen shots for this please. Better again, if you can create a short screen recording and post a link.

Attaching a screenshot. Will try to create a video next time we have a lot of jobs in the queue.

Actually this is on the job page itself. Does not have to be in build now state.

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.

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.

Upgraded to 1.598 and the older jobs are now getting cleaned up.

Ignore the above comment. Wrong jira.

Now when i click configure on a job i get another js un responsive message

A script on this page may be busy, or it may have stopped responding. You can stop the script now, open the script in the debugger, or let the script continue.

Script: http://IP:8080/adjuncts/19e9c96a/org/kohsuke/stapler/codemirror/lib/codemirror.js:1737

I was not sure. JENKINS-26445 was only if we clicked the more button. However this is just being on the job page. After upgrading i am seeing weird issues like slowness scrolling on the page and some times i am not able to click links on the page.

If you feel the same code needs to be fixed for both then we can resolve this as dup.

We can leave it for now and see. Thanks for the quick reply Arpit.

@Arpit: would you be able to test this issue against the 1.598 release and let me know if you're still having issues please?

If the problem persists, please create a screen recording that allows us to see the issue for real. Another option might be for us to do a screenshare over skype (or other), allowing me to see it for real.

@Tom it is not as bad as before but the scrolling is not smooth. Atleast the above JS error goes away once i click stop using the script button. I will try to replicate it and post a recording. Since this is our production jenkins its difficult to create this scenario on demand .

Here is the screencast

https://drive.google.com/file/d/0B829VZ-i0OctRGlwM1JmclBlSDQ/view?usp=sharing

I'm also seeing this issue with Jenkins 1.617. I've noticed it when opening a larger job config and when the build history grows large.

arpitgupta Your screencast is no longer available.

danielbeck looks like i ended up deleting when i cleaned up my google drive. I will try to upload a new one when i get a chance.

The job config issue i have seen when we have a lot of params in the job regardless of how many builds might be in the history so it might be un related.

Would this be a duplicate of https://issues.jenkins-ci.org/browse/JENKINS-26445?