[JIRA] [accurev-plugin] (JENKINS-35388) accurev-plugin parameters
Title: Message Title wbauer edited a comment on JENKINS-35388 Re: accurev-plugin parameters We are seeing the same happening very frequently on Jenkins 1.656 with accurev plugin 0.6.35. Jenkins master is RHEL 6.5.Changing the job config either helps or triggers the problem.There are no accurev-related errors seen in the logs. The depot is visible in teh dropdown in the job config and set.Builds fail with the same issue without and with EnvInject plugin, no difference. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [accurev-plugin] (JENKINS-35388) accurev-plugin parameters
Title: Message Title wbauer commented on JENKINS-35388 Re: accurev-plugin parameters We are seeing the same happening very frequently on Jenkins 1.656 with accurev plugin 0.6.35. Jenkins master is RHEL 6.5. Changing the job config either helps or triggers the problem. There are no accurev-related errors seen in the logs. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [accurev-plugin] (JENKINS-29852) accurev plugin does not pop on workspace anymore
Title: Message Title wbauer created an issue Jenkins / JENKINS-29852 accurev plugin does not pop on workspace anymore Issue Type: Bug Assignee: Scott Tatum Components: accurev-plugin Created: 07/Aug/15 10:02 AM Environment: Jenkins 1.622 on RHEL 6.5, accurev plugin 0.633 Priority: Critical Reporter: wbauer We recently upgraded Jenkins and accurev plugin (from 0.618) and have failed builds due to the workspace not being populated correctly, actually not populated at all in some cases, only updated. Build is done on an explicit workspace and on a specific location on disk. If I have no changes in SCM and no workspace or host change from the last build, there is no pop being done. IF my workspace is missing files or if I cleaned it after the last build, I do not get any file on disk and the build fails. The problem was not there in 0.618 where all workspace logic was in AccurevSCM.java. The functionality is now in AccuRevWorkspaceProcessor.java which does not do a pop on the workspace (as was done before) by default. pop is only done on host change or workspace move.
[JIRA] [analysis-core-plugin] (JENKINS-25405) Plugins depending on Analysis Core plugin fails with NoSuchMethodError
wbauer commented on JENKINS-25405 Plugins depending on Analysis Core plugin fails with NoSuchMethodError Same issue here, Jenkins 1.588, analysis-core 1.64. Rolling back analysis-core to 1.62 made it work again. Looks like the return type of method hudson.plugins.analysis.core.ParserResult.addAnnotations has changed, which breaks the depending plugins calling that method. 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] [core] (JENKINS-11097) Jobs get aborted with Command close created as cause in the stacktrace
wbauer commented on JENKINS-11097 Jobs get aborted with Command close created as cause in the stacktrace This issue is fairly new and looks similar: https://issues.jenkins-ci.org/browse/JENKINS-24761 I see this sporadically on a 1.572 master (RHEL 6.5) and our Windows slaves, Linux and Mac slaves are fine. Was not able to pinpoint how, when or why yet . 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] [remoting] (JENKINS-24761) Jenkin job fails with hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown
wbauer commented on JENKINS-24761 Jenkin job fails with hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown I see this as well, master is RHEL 6.5 linux jenkins version 1.572 and only windows slaves are affected (look s like they loose connection sporadically). Mac and Linux slaves are fine. I was not able to consistently reproduce or pinpoint how, when or why this happens yet - due to time constraints. 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] [parameterized-remote-trigger] (JENKINS-22231) Allow parameterized remote trigger to be a post-build action
wbauer commented on JENKINS-22231 Allow parameterized remote trigger to be a post-build action Hi, I would love to use this in a post-build step instead of inside the actual build steps. My most common use case is to trigger once the originating job is fully done, so as the last step in the post-build actions. 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] [core] (JENKINS-23250) Failed to inspect ... build.xml warnings in jenkins log
wbauer reopened JENKINS-23250 Failed to inspect ... build.xml warnings in jenkins log Hi, I am seeing this with 1.564 when jenkins is starting up (RHEL 6.5). Startup time once was about 5 minutes and now is in the ranges of 2 hours. jenkins.log excerpt below. I have a massive amount of build.xml doesn't exist messages and jenkins takes seconds to process each one, which results in the very long jenkins startup time. WARNING: Failed to inspect /home/nxnbuild/jenkins/jobs/comp.reports (MI_2.4.0 xlinks)/builds/2014-02-06_22-31-35: /home/nxnbuild/jenkins/jobs/comp.reports (MI_2.4.0 xlinks)/builds/2014-02-06_22-31-35/build.xml doesn't exist Jun 25, 2014 10:18:25 AM jenkins.diagnostics.ooom.Problem$Inspector scan WARNING: Failed to inspect /home/nxnbuild/jenkins/jobs/comp.reports (xlink report)/builds/2012-02-27_02-31-31: /home/nxnbuild/jenkins/jobs/comp.reports (xlink report)/builds/2012-02-27_02-31-31/build.xml doesn't exist Jun 25, 2014 10:18:25 AM jenkins.diagnostics.ooom.Problem$Inspector scan WARNING: Failed to inspect /home/nxnbuild/jenkins/jobs/comp.reports (xlink report)/builds/2012-03-29_02-40-31: /home/nxnbuild/jenkins/jobs/comp.reports (xlink report)/builds/2012-03-29_02-40-31/build.xml doesn't exist Jun 25, 2014 10:18:25 AM jenkins.diagnostics.ooom.Problem$Inspector scan WARNING: Failed to inspect /home/nxnbuild/jenkins/jobs/comp.reports (xlink report)/builds/2013-09-24_02-31-26: /home/nxnbuild/jenkins/jobs/comp.reports (xlink report)/builds/2013-09-24_02-31-26/build.xml doesn't exist Jun 25, 2014 10:18:25 AM jenkins.diagnostics.ooom.Problem$Inspector scan WARNING: Failed to inspect /home/nxnbuild/jenkins/jobs/comp.reports (xlink report)/builds/2013-08-12_02-30-42: /home/nxnbuild/jenkins/jobs/comp.reports (xlink report)/builds/2013-08-12_02-30-42/build.xml doesn't exist Jun 25, 2014 10:18:25 AM jenkins.diagnostics.ooom.Problem$Inspector scan WARNING: Failed to inspect /home/nxnbuild/jenkins/jobs/comp.reports (xlink report)/builds/2012-02-13_02-35-21: /home/nxnbuild/jenkins/jobs/comp.reports (xlink report)/builds/2012-02-13_02-35-21/build.xml doesn't exist Jun 25, 2014 10:18:25 AM jenkins.diagnostics.ooom.Problem$Inspector scan WARNING: Failed to inspect /home/nxnbuild/jenkins/jobs/comp.reports (xlink report)/builds/2013-09-27_02-31-14: /home/nxnbuild/jenkins/jobs/comp.reports (xlink report)/builds/2013-09-27_02-31-14/build.xml doesn't exist Jun 25, 2014 10:18:25 AM jenkins.diagnostics.ooom.Problem$Inspector scan WARNING: Failed to inspect /home/nxnbuild/jenkins/jobs/comp.reports (xlink report)/builds/2013-04-17_02-31-14: /home/nxnbuild/jenkins/jobs/comp.reports (xlink report)/builds/2013-04-17_02-31-14/build.xml doesn't exist Jun 25, 2014 10:18:25 AM jenkins.diagnostics.ooom.Problem$Inspector scan WARNING: Failed to inspect /home/nxnbuild/jenkins/jobs/comp.reports (xlink report)/builds/2011-09-05_12-21-31: /home/nxnbuild/jenkins/jobs/comp.reports (xlink report)/builds/2011-09-05_12-21-31/build.xml doesn't exist Jun 25, 2014 10:18:25 AM jenkins.diagnostics.ooom.Problem$Inspector scan WARNING: Failed to inspect /home/nxnbuild/jenkins/jobs/comp.reports (xlink report)/builds/2013-07-14_02-31-05: /home/nxnbuild/jenkins/jobs/comp.reports (xlink report)/builds/2013-07-14_02-31-05/build.xml doesn't exist Jun 25, 2014 10:18:25 AM jenkins.diagnostics.ooom.Problem$Inspector scan WARNING: Failed to inspect /home/nxnbuild/jenkins/jobs/comp.reports (xlink report)/builds/2011-02-02_13-44-57: /home/nxnbuild/jenkins/jobs/comp.reports (xlink report)/builds/2011-02-02_13-44-57/build.xml doesn't exist Jun 25, 2014 10:18:35 AM jenkins.diagnostics.ooom.Problem$Inspector scan WARNING: Failed to inspect /home/nxnbuild/jenkins/jobs/comp.setenv (heartbeat mac)/builds/2013-03-12_02-31-04: /home/nxnbuild/jenkins/jobs/comp.setenv (heartbeat mac)/builds/2013-03-12_02-31-04/build.xml doesn't exist Jun 25, 2014 10:18:35 AM jenkins.diagnostics.ooom.Problem$Inspector scan WARNING: Failed to inspect /home/nxnbuild/jenkins/jobs/comp.setenv (heartbeat mac)/builds/2013-09-27_02-31-14: /home/nxnbuild/jenkins/jobs/comp.setenv (heartbeat mac)/builds/2013-09-27_02-31-14/build.xml doesn't exist Jun 25, 2014 10:18:55 AM jenkins.diagnostics.ooom.Problem$Inspector scan WARNING: Failed to inspect /home/nxnbuild/jenkins/jobs/comp.setenv (heartbeat)/builds/2013-09-27_02-32-36: /home/nxnbuild/jenkins/jobs/comp.setenv (heartbeat)/builds/2013-09-27_02-32-36/build.xml doesn't exist
[JIRA] [core] (JENKINS-14332) Repeated channel/timeout errors from Jenkins slave
wbauer commented on JENKINS-14332 Repeated channel/timeout errors from Jenkins slave Same issue here with Linux SSH slaves with Jenkins 1.564: 14:33:30 Started by user wbauer 14:33:30 EnvInject - Loading node environment variables. 14:33:30 ERROR: SEVERE ERROR occurs 14:33:30 org.jenkinsci.lib.envinject.EnvInjectException: hudson.remoting.ChannelClosedException: channel is already closed 14:33:30 at org.jenkinsci.plugins.envinject.service.EnvironmentVariablesNodeLoader.gatherEnvironmentVariablesNode(EnvironmentVariablesNodeLoader.java:75) 14:33:30 at org.jenkinsci.plugins.envinject.EnvInjectListener.loadEnvironmentVariablesNode(EnvInjectListener.java:81) 14:33:30 at org.jenkinsci.plugins.envinject.EnvInjectListener.setUpEnvironment(EnvInjectListener.java:39) 14:33:30 at hudson.model.AbstractBuild$AbstractBuildExecution.createLauncher(AbstractBuild.java:570) 14:33:30 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:476) 14:33:30 at hudson.model.Run.execute(Run.java:1706) 14:33:30 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 14:33:30 at hudson.model.ResourceController.execute(ResourceController.java:88) 14:33:30 at hudson.model.Executor.run(Executor.java:231) 14:33:30 Caused by: hudson.remoting.ChannelClosedException: channel is already closed 14:33:30 at hudson.remoting.Channel.send(Channel.java:541) 14:33:30 at hudson.remoting.Request.call(Request.java:129) 14:33:30 at hudson.remoting.Channel.call(Channel.java:739) 14:33:30 at hudson.FilePath.act(FilePath.java:1009) 14:33:30 at org.jenkinsci.plugins.envinject.service.EnvironmentVariablesNodeLoader.gatherEnvironmentVariablesNode(EnvironmentVariablesNodeLoader.java:44) 14:33:30 ... 8 more 14:33:30 Caused by: java.io.IOException 14:33:30 at hudson.remoting.Channel.close(Channel.java:1027) 14:33:30 at hudson.slaves.ChannelPinger$1.onDead(ChannelPinger.java:110) 14:33:30 at hudson.remoting.PingThread.ping(PingThread.java:120) 14:33:30 at hudson.remoting.PingThread.run(PingThread.java:81) 14:33:30 Caused by: java.util.concurrent.TimeoutException: Ping started on 1401187729473 hasn't completed at 1401187969473 14:33:30 ... 2 more 14:33:30 Notifying upstream projects of job completion 14:33:30 EnvInject - ERROR - SEVERE ERROR occurs: channel is already closed 14:33:33 Finished: FAILURE 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.
