[JIRA] (JENKINS-11074) LOADING Overlay does not go away - IE 8

2012-07-18 Thread naveen.karn...@baml.com (JIRA)














































naveen karnati
 commented on  JENKINS-11074


LOADING Overlay does not go away - IE 8















Similar issue here. A quick fix is, I have copied "hudson-behavior.js"  "autocomplete-min.js" from old jenkins version (1.410) to our newer jenkins version (1.447), cleared browsing history and it solved the problem. 

In my case culprit is both autocomplete-min.js  hudson-behavior.js
Message: 'YAHOO.util.DataSourceBase.TYPE_JSON' is null or not an object
Line: 7
Char: 343
Code: 0
URI: http:xx/scripts/yui/autocomplete/autocomplete-min.js


Message: Object expected
Line: 681
Char: 9
Code: 0
URI: http:xx/scripts/hudson-behavior.js



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira






[JIRA] (JENKINS-13892) Analysis collector marks some warnings as fixed even though they are not

2012-07-17 Thread naveen.karn...@baml.com (JIRA)














































naveen karnati
 updated  JENKINS-13892


Analysis collector marks some warnings as fixed even though they are not
















Apologies for delayed response. Attached is the build.xml (I could retrieve the xml file from jobconfighistory plugin we are using).

Thanks for your continued support to Jenkins





Change By:


naveen karnati
(17/Jul/12 8:51 AM)




Attachment:


build_may21.xml



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira






[JIRA] (JENKINS-13253) Slave connection reset issues since 1.456

2012-07-17 Thread naveen.karn...@baml.com (JIRA)














































naveen karnati
 commented on  JENKINS-13253


Slave connection reset issues since 1.456















We have similar issues over here. The socket gets disconnected intermittently.

hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset

Jenkins ver. 1.410



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira






[JIRA] (JENKINS-13892) Analysis collector marks some warnings as fixed even though they are not

2012-07-17 Thread naveen.karn...@baml.com (JIRA)














































naveen karnati
 updated  JENKINS-13892


Analysis collector marks some warnings as fixed even though they are not
















oops.. Attached config.xml rather than build.xml in my earlier post. sry.. Attached is the requested build.xml (both reference  failed).

thanks





Change By:


naveen karnati
(17/Jul/12 1:34 PM)




Attachment:


failed_build.xml





Attachment:


reference_build.xml



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira






[JIRA] (JENKINS-13892) Analysis collector marks some warnings as fixed even though they are not

2012-06-01 Thread naveen.karn...@baml.com (JIRA)

 [ 
https://issues.jenkins-ci.org/browse/JENKINS-13892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

naveen karnati updated JENKINS-13892:
-

Attachment: publisher_warnings_config_xml_part.txt

This is a singular problem. Occurs in frequently. Attached is the build 
config.xml during the build fail. 

 Analysis collector marks some warnings as fixed even though they are not
 

 Key: JENKINS-13892
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13892
 Project: Jenkins
  Issue Type: Bug
  Components: analysis-collector, analysis-core
 Environment: Jenkins core version: 1.410
 Static Code Analysis Plug-ins -- 1.38
 FindBugs Plugin -- 4.36
 Warnings Plugin-- 3.28
 Analysis Collector Plugin--- 1.19
Reporter: naveen karnati
Assignee: Ulli Hafner
 Attachments: compilerwarnings.JPG, findbugsresult.JPG, 
 fixed_warnings_tab.JPG, publisher_warnings_config_xml_part.txt, 
 static_analysis_result_error.JPG


 As mentioned over comment 
 https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins?focusedCommentId=60918774#comment-60918774;,
  the Static Analysis Result is showing wrong. 
 We (at our company) are using Jenkins core version 1.410 and Static Code 
 Analysis Plug-ins plugin installed is v1.38. Somehow the result overview is 
 showing wrong. eg: Total warnings are 52, however in the details it shows as 
 40. Surprisingly, the difference 12 warnings went into fixed (even without 
 any change of code).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[JIRA] (JENKINS-13892) Analysis collector marks some warnings as fixed even though they are not

2012-06-01 Thread naveen.karn...@baml.com (JIRA)

[ 
https://issues.jenkins-ci.org/browse/JENKINS-13892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163399#comment-163399
 ] 

naveen karnati edited comment on JENKINS-13892 at 6/1/12 9:20 AM:
--

This is a singular problem. Occurs in frequently. Attached is the build 
config.xml during the build fail. 

The warning numbers of reference build(i.e previous build) is as below. This is 
correct. Due to wrong computation in current build, the next build failed(since 
the reference changed).

FindBugs: 13 warnings from one FindBugs analysis.

Plug-in Result:Success - no threshold has been exceeded
New highscore: only successful builds for 85 days!

Compiler Warnings: 39 warnings.

Plug-in Result:Success - no threshold has been exceeded
New highscore: only successful builds for 46 days!

Static Analysis Warnings: 52 warnings.

Plug-in Result:Success - no threshold has been exceeded
New highscore: only successful builds for 16 days!


  was (Author: naveen_karnati):
This is a singular problem. Occurs in frequently. Attached is the build 
config.xml during the build fail. 
  
 Analysis collector marks some warnings as fixed even though they are not
 

 Key: JENKINS-13892
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13892
 Project: Jenkins
  Issue Type: Bug
  Components: analysis-collector, analysis-core
 Environment: Jenkins core version: 1.410
 Static Code Analysis Plug-ins -- 1.38
 FindBugs Plugin -- 4.36
 Warnings Plugin-- 3.28
 Analysis Collector Plugin--- 1.19
Reporter: naveen karnati
Assignee: Ulli Hafner
 Attachments: compilerwarnings.JPG, findbugsresult.JPG, 
 fixed_warnings_tab.JPG, publisher_warnings_config_xml_part.txt, 
 static_analysis_result_error.JPG


 As mentioned over comment 
 https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins?focusedCommentId=60918774#comment-60918774;,
  the Static Analysis Result is showing wrong. 
 We (at our company) are using Jenkins core version 1.410 and Static Code 
 Analysis Plug-ins plugin installed is v1.38. Somehow the result overview is 
 showing wrong. eg: Total warnings are 52, however in the details it shows as 
 40. Surprisingly, the difference 12 warnings went into fixed (even without 
 any change of code).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[JIRA] (JENKINS-13892) Analysis collector marks some warnings as fixed even though they are not

2012-06-01 Thread naveen.karn...@baml.com (JIRA)

[ 
https://issues.jenkins-ci.org/browse/JENKINS-13892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163399#comment-163399
 ] 

naveen karnati edited comment on JENKINS-13892 at 6/1/12 9:25 AM:
--

This is a singular problem. Occurs in frequently in only one project. Attached 
is the build config.xml during the build fail. 

The warning numbers of reference build(i.e previous build) is as below. This is 
correct. Due to wrong computation in current build, the next build failed(since 
the reference changed).

FindBugs: 13 warnings from one FindBugs analysis.

Plug-in Result:Success - no threshold has been exceeded
New highscore: only successful builds for 85 days!

Compiler Warnings: 39 warnings.

Plug-in Result:Success - no threshold has been exceeded
New highscore: only successful builds for 46 days!

Static Analysis Warnings: 52 warnings.

Plug-in Result:Success - no threshold has been exceeded
New highscore: only successful builds for 16 days!


  was (Author: naveen_karnati):
This is a singular problem. Occurs in frequently. Attached is the build 
config.xml during the build fail. 

The warning numbers of reference build(i.e previous build) is as below. This is 
correct. Due to wrong computation in current build, the next build failed(since 
the reference changed).

FindBugs: 13 warnings from one FindBugs analysis.

Plug-in Result:Success - no threshold has been exceeded
New highscore: only successful builds for 85 days!

Compiler Warnings: 39 warnings.

Plug-in Result:Success - no threshold has been exceeded
New highscore: only successful builds for 46 days!

Static Analysis Warnings: 52 warnings.

Plug-in Result:Success - no threshold has been exceeded
New highscore: only successful builds for 16 days!

  
 Analysis collector marks some warnings as fixed even though they are not
 

 Key: JENKINS-13892
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13892
 Project: Jenkins
  Issue Type: Bug
  Components: analysis-collector, analysis-core
 Environment: Jenkins core version: 1.410
 Static Code Analysis Plug-ins -- 1.38
 FindBugs Plugin -- 4.36
 Warnings Plugin-- 3.28
 Analysis Collector Plugin--- 1.19
Reporter: naveen karnati
Assignee: Ulli Hafner
 Attachments: compilerwarnings.JPG, findbugsresult.JPG, 
 fixed_warnings_tab.JPG, publisher_warnings_config_xml_part.txt, 
 static_analysis_result_error.JPG


 As mentioned over comment 
 https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins?focusedCommentId=60918774#comment-60918774;,
  the Static Analysis Result is showing wrong. 
 We (at our company) are using Jenkins core version 1.410 and Static Code 
 Analysis Plug-ins plugin installed is v1.38. Somehow the result overview is 
 showing wrong. eg: Total warnings are 52, however in the details it shows as 
 40. Surprisingly, the difference 12 warnings went into fixed (even without 
 any change of code).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[JIRA] (JENKINS-13892) Analysis collector marks some warnings as fixed even though they are not

2012-06-01 Thread naveen.karn...@baml.com (JIRA)

[ 
https://issues.jenkins-ci.org/browse/JENKINS-13892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163399#comment-163399
 ] 

naveen karnati edited comment on JENKINS-13892 at 6/1/12 9:26 AM:
--

This is a singular problem. Occurs in frequently in only one project (as of my 
awareness). Attached is the build config.xml during the build fail. 

The warning numbers of reference build(i.e previous build) is as below. This is 
correct. Due to wrong computation in current build, the next build failed(since 
the reference changed).

FindBugs: 13 warnings from one FindBugs analysis.

Plug-in Result:Success - no threshold has been exceeded
New highscore: only successful builds for 85 days!

Compiler Warnings: 39 warnings.

Plug-in Result:Success - no threshold has been exceeded
New highscore: only successful builds for 46 days!

Static Analysis Warnings: 52 warnings.

Plug-in Result:Success - no threshold has been exceeded
New highscore: only successful builds for 16 days!


  was (Author: naveen_karnati):
This is a singular problem. Occurs in frequently in only one project. 
Attached is the build config.xml during the build fail. 

The warning numbers of reference build(i.e previous build) is as below. This is 
correct. Due to wrong computation in current build, the next build failed(since 
the reference changed).

FindBugs: 13 warnings from one FindBugs analysis.

Plug-in Result:Success - no threshold has been exceeded
New highscore: only successful builds for 85 days!

Compiler Warnings: 39 warnings.

Plug-in Result:Success - no threshold has been exceeded
New highscore: only successful builds for 46 days!

Static Analysis Warnings: 52 warnings.

Plug-in Result:Success - no threshold has been exceeded
New highscore: only successful builds for 16 days!

  
 Analysis collector marks some warnings as fixed even though they are not
 

 Key: JENKINS-13892
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13892
 Project: Jenkins
  Issue Type: Bug
  Components: analysis-collector, analysis-core
 Environment: Jenkins core version: 1.410
 Static Code Analysis Plug-ins -- 1.38
 FindBugs Plugin -- 4.36
 Warnings Plugin-- 3.28
 Analysis Collector Plugin--- 1.19
Reporter: naveen karnati
Assignee: Ulli Hafner
 Attachments: compilerwarnings.JPG, findbugsresult.JPG, 
 fixed_warnings_tab.JPG, publisher_warnings_config_xml_part.txt, 
 static_analysis_result_error.JPG


 As mentioned over comment 
 https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins?focusedCommentId=60918774#comment-60918774;,
  the Static Analysis Result is showing wrong. 
 We (at our company) are using Jenkins core version 1.410 and Static Code 
 Analysis Plug-ins plugin installed is v1.38. Somehow the result overview is 
 showing wrong. eg: Total warnings are 52, however in the details it shows as 
 40. Surprisingly, the difference 12 warnings went into fixed (even without 
 any change of code).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[JIRA] (JENKINS-13892) Static analyis plugins

2012-05-24 Thread naveen.karn...@baml.com (JIRA)

 [ 
https://issues.jenkins-ci.org/browse/JENKINS-13892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

naveen karnati updated JENKINS-13892:
-

Summary: Static analyis plugins  (was: Static analyis plugins on MBA)
Description: 
As mentioned over comment 
https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins?focusedCommentId=60918774#comment-60918774;,
 the Static Analysis Result is showing wrong. 
We (at our company) are using Jenkins core version 1.410 and Static Code 
Analysis Plug-ins plugin installed is v1.38. Somehow the result overview is 
showing wrong. eg: Total warnings are 52, however in the details it shows as 
40. Surprisingly, the difference 12 warnings went into fixed (even without any 
change of code).   Appreciate any insights on this

Let me know if you need further info.

Jenkins core version: 1.410
Static Code Analysis Plug-ins -- 1.38
FindBugs Plugin -- 4.36
Warnings Plugin-- 3.28
Analysis Collector Plugin--- 1.19

Thank you. 

  was:
As mentioned over comment 
https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins?focusedCommentId=60918774#comment-60918774;,
 the Static Analysis Result is showing wrong. Let me know if you need further 
info.

Jenkins core version: 1.410
Static Code Analysis Plug-ins -- 1.38
FindBugs Plugin -- 4.36
Warnings Plugin-- 3.28
Analysis Collector Plugin--- 1.19

Thank you. 


 Static analyis plugins
 --

 Key: JENKINS-13892
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13892
 Project: Jenkins
  Issue Type: Bug
  Components: plugin
Reporter: naveen karnati
Assignee: Ulli Hafner
 Attachments: static_analysis_result_error.JPG


 As mentioned over comment 
 https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins?focusedCommentId=60918774#comment-60918774;,
  the Static Analysis Result is showing wrong. 
 We (at our company) are using Jenkins core version 1.410 and Static Code 
 Analysis Plug-ins plugin installed is v1.38. Somehow the result overview is 
 showing wrong. eg: Total warnings are 52, however in the details it shows as 
 40. Surprisingly, the difference 12 warnings went into fixed (even without 
 any change of code).   Appreciate any insights on this
 Let me know if you need further info.
 Jenkins core version: 1.410
 Static Code Analysis Plug-ins -- 1.38
 FindBugs Plugin -- 4.36
 Warnings Plugin-- 3.28
 Analysis Collector Plugin--- 1.19
 Thank you. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[JIRA] (JENKINS-13892) Static analyis plugins on MBA

2012-05-24 Thread naveen.karn...@baml.com (JIRA)
naveen karnati created JENKINS-13892:


 Summary: Static analyis plugins on MBA
 Key: JENKINS-13892
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13892
 Project: Jenkins
  Issue Type: Bug
  Components: plugin
Reporter: naveen karnati
Assignee: Ulli Hafner
 Attachments: static_analysis_result_error.JPG

As mentioned over comment 
https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins?focusedCommentId=60918774#comment-60918774;,
 the Static Analysis Result is showing wrong. Let me know if you need further 
info.

Jenkins core version: 1.410
Static Code Analysis Plug-ins -- 1.38
FindBugs Plugin -- 4.36
Warnings Plugin-- 3.28
Analysis Collector Plugin--- 1.19

Thank you. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[JIRA] (JENKINS-13892) Static analyis plugins

2012-05-24 Thread naveen.karn...@baml.com (JIRA)

 [ 
https://issues.jenkins-ci.org/browse/JENKINS-13892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

naveen karnati updated JENKINS-13892:
-

Attachment: findbugsresult.JPG
fixed_warnings_tab.JPG
compilerwarnings.JPG

Attached is findbugresult, fixed_warnings_tab  compilerwarnings.

Somehow the 12 tests shown as warnings in findbugresult  compilerwarnings, 
went into fixed in the build analysis result.

Sry.. I didn't get when you are requesting to provide build summary for each 
plugin. Is it the console output.

 Static analyis plugins
 --

 Key: JENKINS-13892
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13892
 Project: Jenkins
  Issue Type: Bug
  Components: analysis-collector, analysis-core
Reporter: naveen karnati
Assignee: Ulli Hafner
 Attachments: compilerwarnings.JPG, findbugsresult.JPG, 
 fixed_warnings_tab.JPG, static_analysis_result_error.JPG


 As mentioned over comment 
 https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins?focusedCommentId=60918774#comment-60918774;,
  the Static Analysis Result is showing wrong. 
 We (at our company) are using Jenkins core version 1.410 and Static Code 
 Analysis Plug-ins plugin installed is v1.38. Somehow the result overview is 
 showing wrong. eg: Total warnings are 52, however in the details it shows as 
 40. Surprisingly, the difference 12 warnings went into fixed (even without 
 any change of code).   Appreciate any insights on this
 Let me know if you need further info.
 Jenkins core version: 1.410
 Static Code Analysis Plug-ins -- 1.38
 FindBugs Plugin -- 4.36
 Warnings Plugin-- 3.28
 Analysis Collector Plugin--- 1.19
 Thank you. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira




[JIRA] (JENKINS-13892) Static analyis plugins

2012-05-24 Thread naveen.karn...@baml.com (JIRA)

[ 
https://issues.jenkins-ci.org/browse/JENKINS-13892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163183#comment-163183
 ] 

naveen karnati edited comment on JENKINS-13892 at 5/25/12 3:58 AM:
---

Attached is findbugresult, fixed_warnings_tab  compilerwarnings.

Somehow the 12 tests shown as warnings in find bug result  compiler warnings, 
went into fixed in the build analysis result.

The same build passed in the subsequent runs and somehow the build fails 
intermittently. So I guess it may not be related to duplicates.

Sry.. I didn't get when you are requesting to provide build summary info for 
each plugin. Is it you want console output

Thank you

  was (Author: naveen_karnati):
Attached is findbugresult, fixed_warnings_tab  compilerwarnings.

Somehow the 12 tests shown as warnings in findbugresult  compilerwarnings, 
went into fixed in the build analysis result.

Sry.. I didn't get when you are requesting to provide build summary for each 
plugin. Is it the console output.
  
 Static analyis plugins
 --

 Key: JENKINS-13892
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13892
 Project: Jenkins
  Issue Type: Bug
  Components: analysis-collector, analysis-core
Reporter: naveen karnati
Assignee: Ulli Hafner
 Attachments: compilerwarnings.JPG, findbugsresult.JPG, 
 fixed_warnings_tab.JPG, static_analysis_result_error.JPG


 As mentioned over comment 
 https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins?focusedCommentId=60918774#comment-60918774;,
  the Static Analysis Result is showing wrong. 
 We (at our company) are using Jenkins core version 1.410 and Static Code 
 Analysis Plug-ins plugin installed is v1.38. Somehow the result overview is 
 showing wrong. eg: Total warnings are 52, however in the details it shows as 
 40. Surprisingly, the difference 12 warnings went into fixed (even without 
 any change of code).   Appreciate any insights on this
 Let me know if you need further info.
 Jenkins core version: 1.410
 Static Code Analysis Plug-ins -- 1.38
 FindBugs Plugin -- 4.36
 Warnings Plugin-- 3.28
 Analysis Collector Plugin--- 1.19
 Thank you. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira