-
Bug
-
Resolution: Cannot Reproduce
-
Critical
-
Jenkins Version 1.626
Timestamper Plugin Version 1.7.2
After installing the plugin and enabling the feature in the job, it seems like we are not able to view the logfile after the build had been completed.
Attached is a screeshot that shows the browser hanging while trying to access the console output "log".
Uninstalling the Plugin fixes the issue.
[JENKINS-30394] Browser hangs when opening build log with Timestamper plugin installed
Steven G Brown
added a comment - - Which operating system and browser are you using?
- Does anything appear in the Javascript console?
Steven G Brown
added a comment -
Which operating system and browser are you using?
Does anything appear in the Javascript console?
Jack Yerabutar
added a comment - - Which operating system and browser are you using?
> We have tested this on both mac and windows.
- Does anything appear in the Javascript console?
> A screenshot has been attached with the output in the JavaScript console.
Jack Yerabutar
added a comment -
Which operating system and browser are you using?
> We have tested this on both mac and windows.
Does anything appear in the Javascript console?
> A screenshot has been attached with the output in the JavaScript console.
Jack Yerabutar
added a comment - Got an error while trying to attach a screenshot. Below is the output in the JavaScript console.
GET http://10.39.106.250/jenkins/static/068a7b78/images/16x16/.png 404 (Not Found) (index):1 GET http://10.39.106.250/jenkins/static/068a7b78/images/16x16/.png 404 (Not Found) prototype.js:1585 POST http://10.39.106.250/jenkins/job/TestTimeStampPlugin/com.cloudbees.jenkins.plugins.freeplugins.Notice/instance/ajax 404 (Not Found)Ajax.Request.Class.create.request @ prototype.js:1585Ajax.Request.Class.create.initialize @ prototype.js:1550Object.extend.__method @ prototype.js:452klass @ prototype.js:101f @ (index):30
Jack Yerabutar
added a comment - Got an error while trying to attach a screenshot. Below is the output in the JavaScript console.
GET http: //10.39.106.250/jenkins/ static /068a7b78/images/16x16/.png 404 (Not Found)
(index):1 GET http: //10.39.106.250/jenkins/ static /068a7b78/images/16x16/.png 404 (Not Found)
prototype.js:1585 POST http: //10.39.106.250/jenkins/job/TestTimeStampPlugin/com.cloudbees.jenkins.plugins.freeplugins.Notice/instance/ajax 404 (Not Found)Ajax.Request. Class .create.request @ prototype.js:1585Ajax.Request. Class .create.initialize @ prototype.js:1550Object.extend.__method @ prototype.js:452klass @ prototype.js:101f @ (index):30
Steven G Brown
added a comment - Thanks. Which web browser were you using? Steven G Brown
added a comment - I haven't been able to reproduce this in Windows 10 with Safari, Chrome, IE, Edge or Firefox, or in Debian Linux with Chrome or Iceweasel.
Your Javascript console shows a problem with the CloudBees Free Enterprise Plugins plugin, and I was able to reproduce that error. It tries to access the wrong URL and then refreshes the page every 30 seconds.
Do you have problems opening the console page when the Timestamper plugin is installed, and the CloudBees Free Enterprise Plugins plugin is not?
Steven G Brown
added a comment - I haven't been able to reproduce this in Windows 10 with Safari, Chrome, IE, Edge or Firefox, or in Debian Linux with Chrome or Iceweasel.
Your Javascript console shows a problem with the CloudBees Free Enterprise Plugins plugin, and I was able to reproduce that error. It tries to access the wrong URL and then refreshes the page every 30 seconds.
Do you have problems opening the console page when the Timestamper plugin is installed, and the CloudBees Free Enterprise Plugins plugin is not? Jack Yerabutar
added a comment - I were finally able to reproduce the issue.
It turns out that we've been upgrading Jenkins from the latest release builds of Jenkins v.1.630 to be exact.
We've tried pushing all our live plugins into the latest supported version of Jenkins v.1.609.3 and it seems to be working now.
- Jack
Jack Yerabutar
added a comment - I were finally able to reproduce the issue.
It turns out that we've been upgrading Jenkins from the latest release builds of Jenkins v.1.630 to be exact.
We've tried pushing all our live plugins into the latest supported version of Jenkins v.1.609.3 and it seems to be working now.
Jack
