[JIRA] [remoting] (JENKINS-2452) Cannot install slave agent as Windows service

2014-10-14 Thread chris.we...@jdsu.com (JIRA)















































Chris Welch
 resolved  JENKINS-2452 as Fixed


Cannot install slave agent as Windows service
















Haven't had this issue in a very long time.  Slave setup has been working fine for at least the past 4 years.





Change By:


Chris Welch
(14/Oct/14 2:36 PM)




Status:


Open
Resolved





Resolution:


Fixed



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [jenkins-tracker] (JENKINS-21765) Jenkins occasionally crashing on start up

2014-02-20 Thread chris.we...@jdsu.com (JIRA)














































Chris Welch
 updated  JENKINS-21765


Jenkins occasionally crashing on start up
















Two more crashes since the initial report.  Logs attached





Change By:


Chris Welch
(20/Feb/14 3:16 PM)




Attachment:


hs_err_pid2041.log





Attachment:


hs_err_pid5959.log



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


[JIRA] (JENKINS-12235) FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel

2012-10-19 Thread chris.we...@jdsu.com (JIRA)














































Chris Welch
 commented on  JENKINS-12235


FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel















We are able to work around the problem by adding:

ClientAliveInterval 60

to /etc/ssh/sshd_config on the Jenkins host



























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-12235) FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel

2012-10-18 Thread chris.we...@jdsu.com (JIRA)














































Chris Welch
 commented on  JENKINS-12235


FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel















We consistently get this error on a Linux build slave consistently on jobs that have little output and take a long time (typically > 2 hours).  We are using ssh and I suspect the problem is due to no traffic on the ssh link for this long period.  Using Jenkins 1.434.



























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-14462) cppcheck plugin doesn't show results until a build is successful

2012-07-17 Thread chris.we...@jdsu.com (JIRA)















































Chris Welch
 resolved  JENKINS-14462 as Cannot Reproduce


cppcheck plugin doesn't show results until a build is successful
















Not a defect, our problem.  Our build had a failure in it.





Change By:


Chris Welch
(17/Jul/12 8:39 PM)




Status:


Open
Resolved





Resolution:


Cannot Reproduce



























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-14466) cppcheck plugin fails build even when all severity evaluation check boxes are unchecked.

2012-07-17 Thread chris.we...@jdsu.com (JIRA)















































Chris Welch
 resolved  JENKINS-14466 as Cannot Reproduce


cppcheck plugin fails build even when all severity evaluation check boxes are unchecked.
















Not a problem.  My mistake, our build had a failure in it.





Change By:


Chris Welch
(17/Jul/12 8:38 PM)




Status:


Open
Resolved





Resolution:


Cannot Reproduce



























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-12504) cppcheck-plugin doesn't display the latest source when cppcheck-plugin is the cause of a build failure

2012-07-17 Thread chris.we...@jdsu.com (JIRA)















































Chris Welch
 resolved  JENKINS-12504 as Fixed


cppcheck-plugin doesn't display the latest source when cppcheck-plugin is the cause of a build failure
















Change By:


Chris Welch
(17/Jul/12 8:37 PM)




Status:


Reopened
Resolved





Resolution:


Fixed



























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-12504) cppcheck-plugin doesn't display the latest source when cppcheck-plugin is the cause of a build failure

2012-07-17 Thread chris.we...@jdsu.com (JIRA)












































  
Chris Welch
 updated  JENKINS-12504


cppcheck-plugin doesn't display the latest source when cppcheck-plugin is the cause of a build failure
















My mistake, we had another error that was causing the failure. Issue is closed.



























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-11305) cppcheck has problems handling file paths with a space in them

2012-07-17 Thread chris.we...@jdsu.com (JIRA)














































Chris Welch
 commented on  JENKINS-11305


cppcheck has problems handling file paths with a space in them















This problem appears to be resolved after we installed cppcheck 1.9.  We made no upgrade to Jenkins, just updated the cppcheck plugin.



























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-14466) cppcheck plugin fails build even when all severity evaluation check boxes are unchecked.

2012-07-17 Thread chris.we...@jdsu.com (JIRA)














































Chris Welch
 updated  JENKINS-14466


cppcheck plugin fails build even when all severity evaluation check boxes are unchecked.
















Change By:


Chris Welch
(17/Jul/12 4:09 PM)




Summary:


cppcheck plugin fails build even when
 
 all severity evaluation check boxes are unchecked.





Attachment:


cppcheckscreen.bmp





Environment:


Jenkins 1.434 CentOS 5.7





Description:


cppcheck 1.9When all of the severity evaluation check boxes are unchecked to fail builds from cppcheck, the build still fails.The comment with the severity evaluation check boxes is:"Determines which severity of errors should be considered when evaluating the build status and health."if they are all uncheck, nothing should be considered when evaluation the build status and health.See the attached screen shot, this causes a build failure for us (we have cppcheck errors, but cannot see them due to another bug with the cppcheck plugin).



























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-14466) cppcheck plugin fails build even when

2012-07-17 Thread chris.we...@jdsu.com (JIRA)














































Chris Welch
 created  JENKINS-14466


cppcheck plugin fails build even when 















Issue Type:


Bug



Assignee:


Gregory Boissinot



Components:


cppcheck



Created:


17/Jul/12 4:02 PM



Project:


Jenkins



Priority:


Major



Reporter:


Chris Welch

























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-12504) cppcheck-plugin doesn't display the latest source when cppcheck-plugin is the cause of a build failure

2012-07-17 Thread chris.we...@jdsu.com (JIRA)














































Chris Welch
 reopened  JENKINS-12504


cppcheck-plugin doesn't display the latest source when cppcheck-plugin is the cause of a build failure
















This problem is still not fixed (using plugin 1.9).  We are still seeing old results from the last successful build when cppcheck fails the build.

Very confusing.





Change By:


Chris Welch
(17/Jul/12 2:24 PM)




Resolution:


Fixed





Status:


Resolved
Reopened



























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-12504) cppcheck-plugin doesn't display the latest source when cppcheck-plugin is the cause of a build failure

2012-07-17 Thread chris.we...@jdsu.com (JIRA)












































  
Chris Welch
 updated  JENKINS-12504


cppcheck-plugin doesn't display the latest source when cppcheck-plugin is the cause of a build failure
















This problem is still not fixed.  We are still seeing old results making it difficult to fix the current problems and giving us confusing information.



























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-14462) cppcheck plugin doesn't show results until a build is successful

2012-07-17 Thread chris.we...@jdsu.com (JIRA)














































Chris Welch
 created  JENKINS-14462


cppcheck plugin doesn't show results until a build is successful















Issue Type:


Bug



Assignee:


Gregory Boissinot



Attachments:


cppcheckscreen.bmp



Components:


cppcheck



Created:


17/Jul/12 2:20 PM



Description:


We have setup our projects so that they fail if there are any cppcheck errors. 

Unfortunately, we can't see any results on new projects, because the plugin won't display results until a build is successful.

But, these builds can't be successful until there are no cppcheck errors.  

Suppressing the results display for a failed build adds no value and makes it very difficult to fix the cppcheck errors that are causing the build failure.

Please turn off all logic related to suppressing results display.  The results should be displayed regardless of the status of the build so that cppcheck problems can be investigated and fixed.




Environment:


Jenkins 1.434 on CentOS 5.7 running as VM




Project:


Jenkins



Priority:


Major



Reporter:


Chris Welch

























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