-
Bug
-
Resolution: Fixed
-
Major
-
Observed on a clean install bare-bone Jenkins 1.636. Issue present also after update to 1.637. On a properly working Jenkins, issue becomes present after upgrading from 1.620 to 1.637.
Known previous version without the problem (might not be the last one): 1.620.
Java: OpenJDK 1.8.0.67 on RHEL-6 x86_62, build provided by OS vendor.
Jenkins is installed from Jenkins RHEl repo at http://pkg.jenkins-ci.org/redhat
Jenkisn runs directly (service jenkins start) and is accessed directly (no reverse proxy).
Browsers: Firefox 41, Chrome 46.Observed on a clean install bare-bone Jenkins 1.636. Issue present also after update to 1.637. On a properly working Jenkins, issue becomes present after upgrading from 1.620 to 1.637. Known previous version without the problem (might not be the last one): 1.620. Java: OpenJDK 1.8.0.67 on RHEL-6 x86_62, build provided by OS vendor. Jenkins is installed from Jenkins RHEl repo at http://pkg.jenkins-ci.org/redhat Jenkisn runs directly (service jenkins start) and is accessed directly (no reverse proxy). Browsers: Firefox 41, Chrome 46.
Job status is not updated in the web browser during build. The progress bar appears and the dot starts blinking, but they never move - even when the job is finished. Reloading the page shows proper status (if job is completed) or proper progress (if it is still building).
Problem observed with latest Firefox and Chrome (other browsers not checked). Inspecting AJAX calls in browser's console reveals that AJAX requests are sent each few seconds and all get 200 OK, but the response body is empty. (On a properly working system the response body is not empty while the job is building).
jenkins.log shows no error or exception - in fact even at log level 7, it shows nothing about the AJAX call. It just denotes at INFO level that a job is starting, then that it completes.
