[JIRA] [mailer-plugin] (JENKINS-26740) Failed to set Jenkins Identity header on email. java.lang.NullPointerException
Guy Rozendorn commented on JENKINS-26740 Failed to set Jenkins Identity header on email. java.lang.NullPointerException Also exists in the Mailer plug-in v1.15 on Jenkins 1.598 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] [git] (JENKINS-16732) Cloning repository on a slave raises hudson.util.IOException2: remote file operation failed
Guy Rozendorn
commented on JENKINS-16732
Cloning repository on a slave raises hudson.util.IOException2: remote file operation failed
Applying the following patch over v1.7.0 seems to solve it:
diff --git i/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java w/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java
index 82598d2..8526e4c 100644
--- i/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java
+++ w/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java
@@ -152,7 +152,7 @@ public class CliGitAPIImpl extends LegacyCompatibleGitAPIImpl {
this.gitExe = gitExe;
this.environment = environment;
-launcher = new LocalLauncher(IGitAPI.verbose?listener:TaskListener.NULL);
+launcher = new LocalLauncher(listener);
}
public GitClient subGit(String subdir) {
@@ -1855,7 +1855,7 @@ public class CliGitAPIImpl extends LegacyCompatibleGitAPIImpl {
}
}
if(shouldProxy) {
-final HttpHost proxyHost = new HttpHost(proxy.name, proxy.port);
+final HttpHost proxyHost = new HttpHost(proxy.name, proxy.port);
final HttpRoutePlanner routePlanner = new DefaultProxyRoutePlanner(proxyHost);
clientBuilder.setRoutePlanner(routePlanner);
if (proxy.getUserName() != null && proxy.getPassword() != null)
@@ -1896,7 +1896,7 @@ public class CliGitAPIImpl extends LegacyCompatibleGitAPIImpl {
try {
for (String candidate : candidates) {
HttpGet get = new HttpGet(candidate);
-
+
final CloseableHttpResponse response = client.execute(get);
try{
status = response.getStatusLine().getStatusCode();
Although we've been running this build only for a day now.
I'll report back if it still happens
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] [git] (JENKINS-16732) Cloning repository on a slave raises hudson.util.IOException2: remote file operation failed
Guy Rozendorn commented on JENKINS-16732 Cloning repository on a slave raises hudson.util.IOException2: remote file operation failed Still symptom, different traceback: java.io.IOException: remote file operation failed: C:\Jenkins\workspace\integration-tests at hudson.remoting.Channel@3e89cfcb:host-ci73 at hudson.FilePath.act(FilePath.java:910) at hudson.FilePath.act(FilePath.java:887) at org.jenkinsci.plugins.gitclient.Git.getClient(Git.java:66) at hudson.plugins.git.GitSCM.createClient(GitSCM.java:565) at hudson.plugins.git.GitSCM.createClient(GitSCM.java:557) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:872) at hudson.model.AbstractProject.checkout(AbstractProject.java:1414) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:671) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:580) at hudson.model.Run.execute(Run.java:1676) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: java.io.IOException: Remote call on host-ci73 failed at hudson.remoting.Channel.call(Channel.java:731) at hudson.FilePath.act(FilePath.java:903) ... 13 more Caused by: java.lang.NoClassDefFoundError: Could not initialize class org.jenkinsci.plugins.gitclient.GitClient at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.(CliGitAPIImpl.java:110) at hudson.plugins.git.GitAPI.(GitAPI.java:43) at org.jenkinsci.plugins.gitclient.Git$1.invoke(Git.java:63) at org.jenkinsci.plugins.gitclient.Git$1.invoke(Git.java:54) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2461) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Retrying after 10 seconds java.io.IOException: remote file operation failed: C:\Jenkins\workspace\integration-tests at hudson.remoting.Channel@3e89cfcb:host-ci73 at hudson.FilePath.act(FilePath.java:910) at hudson.FilePath.act(FilePath.java:887) at org.jenkinsci.plugins.gitclient.Git.getClient(Git.java:66) at hudson.plugins.git.GitSCM.createClient(GitSCM.java:565) at hudson.plugins.git.GitSCM.createClient(GitSCM.java:557) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:872) at hudson.model.AbstractProject.checkout(AbstractProject.java:1414) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:671) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:580) at hudson.model.Run.execute(Run.java:1676) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: java.io.IOException: Remote call on host-ci73 failed at hudson.remoting.Channel.call(Channel.java:731) at hudson.FilePath.act(FilePath.java:903) ... 13 more Caused by: java.lang.NoClassDefFoundError: Could not initialize class org.jenkinsci.plugins.gitclient.GitClient at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.(CliGitAPIImpl.java:110) at hudson.plugins.git.GitAPI.(GitAPI.java:43) at org.jenkinsci.plugins.gitclient.Git$1.invoke(Git.java:63) at org.jenkinsci.plugins.gitclient.Git$1.invoke(Git.java:54) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2461) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
[JIRA] [git] (JENKINS-19822) A first time git clone on a slave produce an error
Guy Rozendorn commented on JENKINS-19822 A first time git clone on a slave produce an error scratch that, traceback comes from a different place 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] [git] (JENKINS-19822) A first time git clone on a slave produce an error
Guy Rozendorn commented on JENKINS-19822 A first time git clone on a slave produce an error still happens in our environment, running: Jenkins 1.553 Git plugin 2.0.4 Git Client plug-in 1.6.4 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-1948) Intermittent slave disconnections with secondary symptoms
Guy Rozendorn
edited a comment on JENKINS-1948
Intermittent slave disconnections with secondary symptoms
This week we changed all our 80± slaves from using the SSHLauncher to use the CommandLauncher, which launches strace -t -s 4096 ssh ..., which the following lines in .ssh/config:
TCPKeepAlive yes
ServerAliveInterval 10
ServerAliveCountMax 10
LogLevel DEBUG
The reason using strace is to get a clue if the connection is dropped first, or the master decides it is dead.
In one of the job executions (which started at 00:00:56 we get this in the log:
Started by timer
Building remotely on host-ci66 in workspace /root/jenkins/workspace/mainline-bdist-develop
Deleting project workspace... Checkout:mainline-bdist-develop / /root/jenkins/workspace/mainline-bdist-develop - hudson.remoting.Channel@27ecbe67:host-ci66
Using strategy: Default
Last Built Revision: Revision ff29df8b003dde47573ddfb0b463351baee6dea3 (origin/develop)
FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel
hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel
at hudson.remoting.Request.call(Request.java:174)
at hudson.remoting.Channel.call(Channel.java:722)
at hudson.FilePath.act(FilePath.java:894)
at hudson.FilePath.act(FilePath.java:878)
at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:942)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1108)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1369)
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:676)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:581)
at hudson.model.Run.execute(Run.java:1593)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:242)
Caused by: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel
at hudson.remoting.Request.abort(Request.java:299)
at hudson.remoting.Channel.terminate(Channel.java:782)
at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69)
Caused by: java.io.IOException: Unexpected termination of the channel
at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50)
Caused by: java.io.EOFException
at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2595)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1315)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:369)
at hudson.remoting.Command.readFrom(Command.java:92)
at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:59)
at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)
and the slave.log ends with this:
00:00:56 select(7, [3 4], [3 5], NULL, {10, 0}) = 4 (in [3 4], out [3 5], left {9, 97})
00:00:56 read(4, "\10\0\245\231\255B,\304\304\7\23\3\0\\7\0\0d\0\0\0hudson/plugins/git/browser/FisheyeGitRepositoryBrowser$FisheyeGitRepositoryBrowserDescriptor$1.class\265U{O\23A\20\377m)\\\251\247\205\"\240@\364\264UK\21\17|\240\370\226\332\"Z5\341\225h\214\361\350-\355\312q[\357\256\5\376\364c\370-0\0214\232\370\1\374P\306\331k!&\0264&m\2567\2733\263\363\370\315\314\336\217\237_\277\3\230\304\223n\34\303\250ze\343H`L\303\3058\242\30\217\23\347R\f\246\242\23qR\274\34\303\25E\257j\270\246\230S\32\256k\270\301p\254n9\351U\341Z\316\262\345\3248C\262\370\326\252[\246c\271es!\360\204[\276\305\320\25T\204\237\236\320@\353s\5\341W\370\26\237\25\301<\257J_\4\322\333\232\361\344\206\317\275\207\334/y\242J\34\6}\316u\271\227s,\337\347>\303\353b\245f\373\3225\253N\255,\\\337,\213\300\\i\0343\0171\231\376'w*\306\333\302\25\301]\6?\323^W\177\0024\272\314\20\315I\233\340K\24\205\313\237\325\326W\270\267h\2558!\240\262\244\320\365\204\3327\231Q\5(\3\30\336\2645\330\364$!\323Y\252\360\322\32\303\251\314\350\236\263Z \34\263 \275u\252\272\260\255@H\227\24\31E\326\337HOHs\356y~\263\304\253MY|\177\343k\270M\373\5Y\363J\274 T:\306!\301\\R\366\10\230\274[rH\342\226\237\362\240\"m\35wpWG\22\3:z\320\253c\20\367\250iB\347.\17\314\245\371\242\342\335\327\361\0003\f\232\362\220\337\342:rx\250!\257\243\0\203\341\352\"\341h\3
[JIRA] [core] (JENKINS-1948) Intermittent slave disconnections with secondary symptoms
Guy Rozendorn
commented on JENKINS-1948
Intermittent slave disconnections with secondary symptoms
This week we changed all our 80± slaves from using the SSHLauncher to use the CommandLauncher, which launches strace -t -s 4096 ssh ..., which the following lines in .ssh/config:
TCPKeepAlive yes
ServerAliveInterval 10
ServerAliveCountMax 10
LogLevel DEBUG
The reason using strace is to get a clue if the connection is dropped first, or the master decides it is dead.
In one of the job executions (which started at 00:00:56 we get this in the log:
Started by timer
Building remotely on host-ci66 in workspace /root/jenkins/workspace/mainline-bdist-develop
Deleting project workspace... Checkout:mainline-bdist-develop / /root/jenkins/workspace/mainline-bdist-develop - hudson.remoting.Channel@27ecbe67:host-ci66
Using strategy: Default
Last Built Revision: Revision ff29df8b003dde47573ddfb0b463351baee6dea3 (origin/develop)
FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel
hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel
at hudson.remoting.Request.call(Request.java:174)
at hudson.remoting.Channel.call(Channel.java:722)
at hudson.FilePath.act(FilePath.java:894)
at hudson.FilePath.act(FilePath.java:878)
at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:942)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1108)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1369)
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:676)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:581)
at hudson.model.Run.execute(Run.java:1593)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:242)
Caused by: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel
at hudson.remoting.Request.abort(Request.java:299)
at hudson.remoting.Channel.terminate(Channel.java:782)
at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69)
Caused by: java.io.IOException: Unexpected termination of the channel
at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50)
Caused by: java.io.EOFException
at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2595)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1315)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:369)
at hudson.remoting.Command.readFrom(Command.java:92)
at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:59)
at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)
and the slave.log ends with this:
00:00:56 select(7, [3 4], [3 5], NULL, {10, 0}) = 4 (in [3 4], out [3 5], left {9, 97})
00:00:56 read(4, "\10\0\245\231\255B,\304\304\7\23\3\0\\7\0\0d\0\0\0hudson/plugins/git/browser/FisheyeGitRepositoryBrowser$FisheyeGitRepositoryBrowserDescriptor$1.class\265U{O\23A\20\377m)\\\251\247\205\"\240@\364\264UK\21\17|\240\370\226\332\"Z5\341\225h\214\361\350-\355\312q[\357\256\5\376\364c\370-0\0214\232\370\1\374P\306\331k!&\0264&m\2567\2733\263\363\370\315\314\336\217\237_\277\3\230\304\223n\34\303\250ze\343H`L\303\3058\242\30\217\23\347R\f\246\242\23qR\274\34\303\25E\257j\270\246\230S\32\256k\270\301p\254n9\351U\341Z\316\262\345\3248C\262\370\326\252[\246c\271es!\360\204[\276\305\320\25T\204\237\236\320@\353s\5\341W\370\26\237\25\301<\257J_\4\322\333\232\361\344\206\317\275\207\334/y\242J\34\6}\316u\271\227s,\337\347>\303\353b\245f\373\3225\253N\255,\\\337,\213\300\\i\0343\0171\231\376'w*\306\333\302\25\301]\6?\323^W\177\0024\272\314\20\315I\233\340K\24\205\313\237\325\326W\270\267h\2558!\240\262\244\320\365\204\3327\231Q\5(\3\30\336\2645\330\364$!\323Y\252\360\322\32\303\251\314\350\236\263Z \34\263 \275u\252\272\260\255@H\227\24\31E\326\337HOHs\356y~\263\304\253MY|\177\343k\270M\373\5Y\363J\274 T:\306!\301\\R\366\10\230\274[rH\342\226\237\362\240\"m\35wpWG\22\3:z\320\253c\20\367\250iB\347.\17\314\245\371\242\342\335\327\361\0003\f\232\362\220\337\342:rx\250!\257\243\0\203\341\352\"\341h\320c\3
[JIRA] [core] (JENKINS-12235) FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel
Guy Rozendorn commented on JENKINS-12235 FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel After update all our jobs to yield output every 10 seconds this occurs less frequent, but it still happens few times a week. 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] [core] (JENKINS-12235) FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel
Guy Rozendorn commented on JENKINS-12235 FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel We had some issues in our lab, which forced us to re-install all of our slaves (84 and counting). We are still experiencing this issue It seems that after this happens, the slave remains connected to Jenkins. However, I can't tell what happens if you try to run another job on it, because we revert the slave VM from snapshot after every run (whether it is successful or not) 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] [core] (JENKINS-12235) FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel
Guy Rozendorn commented on JENKINS-12235 FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel Looking at our master while Jenkins is alive (no job is running), Jenkin's java process takes 100% of one of the CPUs Tasks: 84 total, 1 running, 83 sleeping, 0 stopped, 0 zombie %Cpu(s): 51.4 us, 0.0 sy, 0.0 ni, 48.6 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem: 8178392 total, 7231500 used, 946892 free, 381796 buffers KiB Swap: 8386556 total,20888 used, 8365668 free, 5538224 cached PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 12077 jenkins 20 0 5229m 873m 7428 S 99.7 10.9 11621:35 java does anyone here know how/has references on how to debug this? 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] [core] (JENKINS-12235) FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel
Guy Rozendorn commented on JENKINS-12235 FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel Zhijun Xu, TCPKeepAlive yes is the default, which doesn't work either 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] [core] (JENKINS-12235) FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel
Guy Rozendorn commented on JENKINS-12235 FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel We set the following on all our slaves: ClientAliveCountMax 99 ClientAliveInterval 60 TCPKeepAlive no rebooted them all, and still getting this exception 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] [core] (JENKINS-12235) FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel
Guy Rozendorn edited a comment on JENKINS-12235 FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel Although our master node has 10 executors (left for tied jobs only), this happens when there's a single job running all over the jenkins instance, and its running (and failing) on a different slave. 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] [core] (JENKINS-12235) FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel
Guy Rozendorn commented on JENKINS-12235 FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel Although our master node has 10 executors, this happens when there's a single job running all over the jenkins instance, and its running (and failing) on a different slave. 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] [core] (JENKINS-12235) FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel
Guy Rozendorn commented on JENKINS-12235 FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel I added a print every ten seconds, still happens: ( 2013-29-27 17:29:07 running ) ( 2013-29-27 17:29:17 running ) ( 2013-29-27 17:29:27 running ) ( 2013-29-27 17:29:37 running ) ( 2013-29-27 17:29:47 running ) ( 2013-29-27 17:29:57 running ) ( 2013-30-27 17:30:07 running ) FATAL: Unable to delete script file C:\Users\Administrator\hudson7142602309142296785.py hudson.util.IOException2: remote file operation failed: C:\Users\Administrator\hudson7142602309142296785.py at hudson.remoting.Channel@6e47e0a6:host-ci38 at hudson.FilePath.act(FilePath.java:901) at hudson.FilePath.act(FilePath.java:878) at hudson.FilePath.delete(FilePath.java:1263) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:101) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:60) at hudson.plugins.templateproject.ProxyBuilder.perform(ProxyBuilder.java:87) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:586) at hudson.model.Run.execute(Run.java:1593) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:242) Caused by: hudson.remoting.ChannelClosedException: channel is already closed at hudson.remoting.Channel.send(Channel.java:524) at hudson.remoting.Request.call(Request.java:129) at hudson.remoting.Channel.call(Channel.java:722) at hudson.FilePath.act(FilePath.java:894) ... 14 more Caused by: hudson.remoting.Channel$OrderlyShutdown at hudson.remoting.Channel$CloseCommand.execute(Channel.java:900) at hudson.remoting.Channel$2.handle(Channel.java:465) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Caused by: Command close created at at hudson.remoting.Command.(Command.java:56) at hudson.remoting.Channel$CloseCommand.(Channel.java:894) at hudson.remoting.Channel$CloseCommand.(Channel.java:892) at hudson.remoting.Channel.close(Channel.java:975) at hudson.remoting.Channel.close(Channel.java:958) at hudson.remoting.Channel$CloseCommand.execute(Channel.java:899) ... 2 more FATAL: hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown at hudson.remoting.Request.call(Request.java:174) at hudson.remoting.Channel.call(Channel.java:722) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:162) at sun.proxy.$Proxy38.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:915) at hudson.Launcher$ProcStarter.join(Launcher.java:360) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:91) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:60) at hudson.plugins.templateproject.ProxyBuilder.perform(ProxyBuilder.java:87) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:586) at hudson.model.Run.execute(Run.java:1593) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:242) Caused by: hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown at hudson.remoting.Request.abort(Request.java:299) at hudson.remoting.Channel.terminate(Channel.java:782) at hudson.remoting.Channel$CloseCommand.execute(Channel.java:900) at hudson.remoting.Channel$2.handle(Channel.java:465) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Caused by: hudson.remoting.Channel$OrderlyShutdown ... 3 more Caused by: Command close created at at hudson.remoting.Command.(Command.ja
[JIRA] [core] (JENKINS-12235) FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel
Guy Rozendorn edited a comment on JENKINS-12235 FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel This happens across all our slaves, windows, redhat, ubuntu. We have a little bit more than 100 jobs, and we keep logs for the last 10 runs of each job. Over the last 10 runs, we've seen this 14 times on Windows, 26 times on the other platforms. Everything runs over SSH (cygwin on windows) with the default settings: TCPKeepAlive: yes ClientAliveCountMax: 3 ClientAliveInterval: 0 It doesn't look related to the output - this fails randomly in different steps, some with no output for minutes, some with no output for only a few seconds 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] [core] (JENKINS-12235) FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel
Guy Rozendorn commented on JENKINS-12235 FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel This happens across all our slaves, windows, redhat, ubuntu. We have a little bit more than 100 jobs, and we keep logs for the last 10 runs of each job. Over the last 10 runs, we've seen this 14 times on Windows, 26 times on the other platforms. Everything runs over SSH (cygwin on windows) with the default settings: TCPKeepAlive: yes ClientAliveCountMax: 3 ClientAliveInterval: 0 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] [ssh-slaves] (JENKINS-13237) Unsuccessful SSH slave start do not timeout and cannot be retry, even manually
Guy Rozendorn commented on JENKINS-13237 Unsuccessful SSH slave start do not timeout and cannot be retry, even manually Looks related to JENKINS-13131, did you try waiting for 15 minutes and see if your slaves reconnect? 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] [ssh-slaves] (JENKINS-13131) SSH may stale for 15 minutes after slave restart
Guy Rozendorn commented on JENKINS-13131 SSH may stale for 15 minutes after slave restart more than a year later, and we're still dealing daily with this issue 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-16732) Cloning repository on a slave raises hudson.util.IOException2: remote file operation failed
Guy Rozendorn commented on JENKINS-16732 Cloning repository on a slave raises hudson.util.IOException2: remote file operation failed Debugging this for a bit. With process explorer, I see that after this failure, there are four handles left open: C:\jenkins\workspace\testing-git-failures-2\.git.objects\pack\pack- 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-10197) Matrix jobs default to "locked" (and are difficult to delete)
Guy Rozendorn commented on JENKINS-10197 Matrix jobs default to "locked" (and are difficult to delete) Still happens in 1.500 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-12797) "Don't Keep this build forever" button doesn't work on some matrix job and prevent removing old build
Guy Rozendorn commented on JENKINS-12797 "Don't Keep this build forever" button doesn't work on some matrix job and prevent removing old build Still happens, on Jenkins 1.500 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-16732) Cloning repository on a slave raises hudson.util.IOException2: remote file operation failed
Guy Rozendorn commented on JENKINS-16732 Cloning repository on a slave raises hudson.util.IOException2: remote file operation failed Disconnecting and reconnecting the slave helps, but this is only a workaround 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-16732) Cloning repository on a slave raises hudson.util.IOException2: remote file operation failed
Guy Rozendorn commented on JENKINS-16732 Cloning repository on a slave raises hudson.util.IOException2: remote file operation failed Okay, its happening mostly on the Windows slaves. When this happens, Jenkins can execute shell commands on the slave (with jobs that do not have SCM), but every Git command fails. 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-16732) Cloning repository on a slave raises hudson.util.IOException2: remote file operation failed
Guy Rozendorn created JENKINS-16732 Cloning repository on a slave raises hudson.util.IOException2: remote file operation failed Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: git Created: 09/Feb/13 10:44 AM Description: Running: Jenkins 1.500 Git plugin 1.1.26 In this example, this issue occurred on a Windows host, connected through SSH (cygwin). It happens on non-windows slaves as well. We didn't find a test case which recreates this in 100%. Building remotely on host-ci31 in workspace C:\jenkins\workspace\winver Deleting project workspace... Checkout:winver / C:\jenkins\workspace\winver - hudson.remoting.Channel@144c5230:host-ci31 Using strategy: Default Cloning the remote Git repository Cloning repository git://gitserver/host/winver.git git --version git version 1.8.0.msysgit.0 Fetching upstream changes from git://gitserver/host/winver.git Commencing build of Revision da78c0a621cee24b3632a272918492a73b2b4417 (origin/develop) Checking out Revision da78c0a621cee24b3632a272918492a73b2b4417 (origin/develop) hudson.util.IOException2: remote file operation failed: C:\jenkins\workspace\winver at hudson.remoting.Channel@144c5230:host-ci31 at hudson.FilePath.act(FilePath.java:861) at hudson.FilePath.act(FilePath.java:838) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1231) at hudson.model.AbstractProject.checkout(AbstractProject.java:1331) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:682) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:587) at hudson.model.Run.execute(Run.java:1557) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Caused by: java.io.IOException: Remote call on channel failed at hudson.remoting.Channel.call(Channel.java:681) at hudson.FilePath.write(FilePath.java:1585) at hudson.plugins.git.GitSCM.computeChangeLog(GitSCM.java:1305) at hudson.plugins.git.GitSCM.access$1300(GitSCM.java:72) at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1273) at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1231) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2348) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.NoClassDefFoundError: hudson/remoting/RemoteClassLoader$RemoteIClassLoader at hudson.remoting.RemoteClassLoader.export(RemoteClassLoader.java:395) at hudson.remoting.UserRequest.(UserRequest.java:69) at hudson.remoting.Channel.call(Channel.java:671) ... 15 more Retrying after 10 seconds Checkout:winver / C:\jenkins\workspace\winver - hudson.remoting.Channel@144c5230:host-ci31 Using strategy: Default Fetching changes from 1 remote Git repository Fetching upstream changes from git://gitserver/host/winver.git Commencing build of Revision da78c0a621cee24b3632a272918492a73b2b4417 (origin/develop) Checking out Revision da78c0a621cee24b3632a272918492a73b2b4417 (origin/develop) hudson.util.IOException2: remote file operation failed: C:\jenkins\workspace\winver at hudson.remoting.Channel@144c5230:host-ci31 at hudson.FilePath.act(FilePath.java:861) at hudson.FilePath.act(FilePath.java:838) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1231) at hudson.model.AbstractProject.checkout(AbstractProject.java:1331) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(Abstract
[JIRA] (JENKINS-16732) Cloning repository on a slave raises hudson.util.IOException2: remote file operation failed
Guy Rozendorn commented on JENKINS-16732 Cloning repository on a slave raises hudson.util.IOException2: remote file operation failed We don't use any other SCM Next time this happens we will try to run a job on the subject host w/o involving the git plugin, just to verify that the host is responding 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-15713) Currently running builds are not returned in the APIs
Guy Rozendorn
created JENKINS-15713
Currently running builds are not returned in the APIs
Issue Type:
Bug
Affects Versions:
current
Assignee:
Nicolas De Loof
Components:
build-flow, build-publisher
Created:
04/Nov/12 2:23 PM
Description:
We are running Jenkins ver 1.488, consider the following scenario:
You've started build number 705 for a job named get_infinidat_logs
While the job is running, you query the JOB APIs (here we look at the JOSN API for example).
The build currently running is not in the JSON response (see the output below).
This happens on all the APIs.
This was working as expected in version 1.484
http://ci.infinidat.com/job/get_infinidat_logs/api/json?pretty=true
{
actions: [],
description: "Job to collect logs from infiniboxes",
displayName: "get_infinidat_logs",
displayNameOrNull: null,
name: "get_infinidat_logs",
url: "http://ci.infinidat.com/job/get_infinidat_logs/",
buildable: true,
builds: [
{
number: 704,
url: "http://ci.infinidat.com/job/get_infinidat_logs/704/"
},
{
number: 703,
url: "http://ci.infinidat.com/job/get_infinidat_logs/703/"
},
{
number: 702,
url: "http://ci.infinidat.com/job/get_infinidat_logs/702/"
},
{
number: 701,
url: "http://ci.infinidat.com/job/get_infinidat_logs/701/"
},
{
number: 700,
url: "http://ci.infinidat.com/job/get_infinidat_logs/700/"
},
{
number: 699,
url: "http://ci.infinidat.com/job/get_infinidat_logs/699/"
},
{
number: 698,
url: "http://ci.infinidat.com/job/get_infinidat_logs/698/"
},
{
number: 697,
url: "http://ci.infinidat.com/job/get_infinidat_logs/697/"
},
{
number: 696,
url: "http://ci.infinidat.com/job/get_infinidat_logs/696/"
},
{
number: 695,
url: "http://ci.infinidat.com/job/get_infinidat_logs/695/"
},
{
number: 694,
url: "http://ci.infinidat.com/job/get_infinidat_logs/694/"
},
{
number: 693,
url: "http://ci.infinidat.com/job/get_infinidat_logs/693/"
},
{
number: 692,
url: "http://ci.infinidat.com/job/get_infinidat_logs/692/"
},
{
number: 691,
url: "http://ci.infinidat.com/job/get_infinidat_logs/691/"
},
{
number: 690,
url: "http://ci.infinidat.com/job/get_infinidat_logs/690/"
},
{
number: 689,
url: "http://ci.infinidat.com/job/get_infinidat_logs/689/"
},
{
number: 688,
url: "http://ci.infinidat.com/job/get_infinidat_logs/688/"
},
{
number: 687,
url: "http://ci.infinidat.com/job/get_infinidat_logs/687/"
},
{
number: 686,
url: "http://ci.infinidat.com/job/get_infinidat_logs/686/"
},
{
number: 685,
url: "http://ci.infinidat.com/job/get_infinidat_logs/685/"
},
{
number: 684,
url: "http://ci.infinidat.com/job/get_infinidat_logs/684/"
},
{
number: 683,
url: "http://ci.infinidat.com/job/get_infinidat_logs/683/"
},
{
number: 682,
url: "http://ci.infinidat.com/job/get_infinidat_logs/682/"
},
{
number: 681,
url: "http://ci.infinidat.com/job/get_infinidat_logs/681/"
},
{
number: 680,
url: "http://ci.infinidat.com/job/get_infinidat_logs/680/"
},
{
number: 679,
url: "http://ci.infinidat.com/job/get_infinidat_logs/679/"
},
{
number: 678,
url: "http://ci.infinidat.com/job/get_infinidat_logs/678/"
},
{
number: 677,
url: "http://ci.infinidat.com/job/get_infinidat_logs/677/"
},
{
number: 676,
url: "http://ci.infinidat.com/job/get_infinidat_logs/676/"
},
{
number: 675,
url: "http://ci.infinidat.com/job/get_infinidat_logs/675/"
},
{
number: 674,
url: "http://ci.infinidat.com/job/get_infinidat_logs/674/"
},
{
number: 673,
url: "http://ci.infinidat.com/job/get_infinidat_logs/673/"
},
{
number: 672,
url: "http://ci.infinidat.com/job/get_infinidat_logs/672/"
},
{
number: 671,
url: "http://ci.infinidat.com/job/get_infinidat_logs/671/"
},
{
number: 670,
url: "http://ci.infinidat.com/job/get_infinidat_logs/670/"
},
{
number: 669,
url: "http://ci.infinidat.com/job/get_infinidat_logs/669/"
},
{
number: 668,
url: "http://ci.infinidat.com/job/get_infinidat_logs/668/"
},
{
number: 667,
url: "http://ci.infinidat.com/job/get_infinidat_logs/667/"
},
{
number: 666,
url: "http://ci.infinidat.com/job/get_infinidat_logs/666/"
},
{
number: 665,
url: "http://ci.infinidat.com/job/get_infinidat_l
[JIRA] (JENKINS-14785) Add support for slicing matrix job configuration
Guy Rozendorn reopened JENKINS-14785 Add support for slicing matrix job configuration What I meant it to slice the "Configuration Matrix" for matrix jobs Change By: Guy Rozendorn (25/Sep/12 11:50 PM) Resolution: Cannot Reproduce 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-14784) Add support for the "execute python script" slicer
Guy Rozendorn updated JENKINS-14784 Add support for the "execute python script" slicer Change By: Guy Rozendorn (14/Aug/12 2:24 PM) Issue Type: Bug New Feature 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-14785) Add support for slicing matrix job configuration
Guy Rozendorn created JENKINS-14785 Add support for slicing matrix job configuration Issue Type: New Feature Assignee: mdonohue Components: configurationslicing Created: 14/Aug/12 2:24 PM Project: Jenkins Priority: Major Reporter: Guy Rozendorn 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-14784) Add support for the "execute python script" slicer
Guy Rozendorn created JENKINS-14784 Add support for the "execute python script" slicer Issue Type: Bug Assignee: mdonohue Components: configurationslicing Created: 14/Aug/12 2:22 PM Project: Jenkins Priority: Major Reporter: Guy Rozendorn 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-13131) SSH may stale for 15 minutes after slave restart
Guy Rozendorn created JENKINS-13131: --- Summary: SSH may stale for 15 minutes after slave restart Key: JENKINS-13131 URL: https://issues.jenkins-ci.org/browse/JENKINS-13131 Project: Jenkins Issue Type: Bug Components: ssh-slaves Affects Versions: current Reporter: Guy Rozendorn Assignee: Kohsuke Kawaguchi Priority: Critical We often reboot our slaves. Most of the time they reconnect quickly, but every one of ten slaves just does not reconnect -- in the slave log page we see the circle turning and without any test. After 15-20 minutes it begins to work. While we wait for this to work, we can manually ssh to the server without any problem. -- 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-12796) support templating build steps
[ https://issues.jenkins-ci.org/browse/JENKINS-12796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guy Rozendorn closed JENKINS-12796. --- Resolution: Cannot Reproduce Didn't see the option before. it works. > support templating build steps > -- > > Key: JENKINS-12796 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12796 > Project: Jenkins > Issue Type: New Feature > Components: template-project >Reporter: Guy Rozendorn >Assignee: huybrechts > > We have a lot of jobs that only differ by: > * The slaves the execute the job (different matrixes) > * The git repositories they pull > Until now we manually copied/synced the configuration of all the jobs (around > 20), and we are tired of it. > We looked at the template plugin, but its not enough since the jobs using the > template do not take the build steps of it. -- 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-12796) support templating build steps
Guy Rozendorn created JENKINS-12796: --- Summary: support templating build steps Key: JENKINS-12796 URL: https://issues.jenkins-ci.org/browse/JENKINS-12796 Project: Jenkins Issue Type: New Feature Components: template-project Reporter: Guy Rozendorn Assignee: huybrechts We have a lot of jobs that only differ by: * The slaves the execute the job (different matrixes) * The git repositories they pull Until now we manually copied/synced the configuration of all the jobs (around 20), and we are tired of it. We looked at the template plugin, but its not enough since the jobs using the template do not take the build steps of it. -- 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
