[JIRA] (JENKINS-41211) SocketTimeoutException at Build/Publish Docker Container step
Title: Message Title Alexander Uvizhev created an issue Jenkins / JENKINS-41211 SocketTimeoutException at Build/Publish Docker Container step Issue Type: Bug Assignee: magnayn Components: docker-plugin Created: 2017/Jan/19 10:55 AM Environment: Jenkins = 2.41, Docker plugin = 0.16.2, SSH Slaves plugin = 1.12 Ubuntu pkg: docker-engine = 1.12.3-0~trusty Priority: Minor Reporter: Alexander Uvizhev I get this stacktrace at the end of Build/Publish Docker Container step when container building is finishing: java.lang.RuntimeException: java.net.SocketTimeoutException: Read timed out at shaded.com.google.common.base.Throwables.propagate(Throwables.java:160) at com.github.dockerjava.core.async.ResultCallbackTemplate.getFirstError(ResultCallbackTemplate.java:133) at com.github.dockerjava.core.async.ResultCallbackTemplate.awaitCompletion(ResultCallbackTemplate.java:94) at com.github.dockerjava.core.command.BuildImageResultCallback.awaitImageId(BuildImageResultCallback.java:43) at com.nirima.jenkins.plugins.docker.builder.DockerBuilderPublisher$Run$1.invoke(DockerBuilderPublisher.java:291) at com.nirima.jenkins.plugins.docker.builder.DockerBuilderPublisher$Run$1.invoke(DockerBuilderPublisher.java:274) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2731) at hudson.remoting.UserRequest.perform(UserRequest.java:153) at hudson.remoting.UserRequest.perform(UserRequest.java:50) at hudson.remoting.Request$2.run(Request.java:336) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266)
[JIRA] (JENKINS-27039) Option for input or stage step to cancel older executions
Title: Message Title Alexander Uvizhev edited a comment on JENKINS-27039 Re: Option for input or stage step to cancel older executions [~michaelneale] milestone does not help with this, my builds still run concurrently and none is aborted. For milestone to work newer build should somehow run faster then older one so to pass any of milestones prior. How is this possible at all? The only case I see is when older build is stuck for some reason so new one outrun it and abort it hence. UPD: I understood we speak of different scenarios. In my case there's no input steps, just stages. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-27039) Option for input or stage step to cancel older executions
Title: Message Title Alexander Uvizhev commented on JENKINS-27039 Re: Option for input or stage step to cancel older executions Michael Neale milestone does not help with this, my builds still run concurrently and none is aborted. For milestone to work newer build should somehow run faster then older one so to pass any of milestones prior. How is this possible at all? The only case I see is when older build is stuck for some reason so new one outrun it and abort it hence. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-27039) Option for input or stage step to cancel older executions
Title: Message Title Alexander Uvizhev commented on JENKINS-27039 Re: Option for input or stage step to cancel older executions cancel older builds for a specific PR, if more pushed commits triggered a new build? But not cancel any builds for a different PR Automatic if you are using a multibranch project. Jesse Glick do you mean running PR build in multibranch should abort if new build for same PR is scheduled? I ask because it does not work for me so I wonder if I understand you right. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-client-plugin] (JENKINS-26757) Error cloning remote repo 'origin' with username:passw...@bitbucket.org URLs
Title: Message Title Alexander Uvizhev commented on JENKINS-26757 Re: Error cloning remote repo 'origin' with username:passw...@bitbucket.org URLs Mark Waite yes, I use GitHub Enterprise. I googled this bug and didn't see any other related to GitHub. Now I cannot reproduce the first case but in second I tried both anonymous repo fetching and specifying credentials (not directly in URL). I already put my private key into Jenkins Credentials and it seems to work since I can execute buildsteps on JClouds slaves, but cannot fetch repo. If there's GitHub related issue please point me to it. Thanks in advance. 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] [git-client-plugin] (JENKINS-26757) Error cloning remote repo 'origin' with username:passw...@bitbucket.org URLs
Title: Message Title Alexander Uvizhev commented on JENKINS-26757 Re: Error cloning remote repo 'origin' with username:passw...@bitbucket.org URLs I've the same problem and in one case it appeared in jobs running on 'master'. What solved problem in this case was putting ssh key in jenkins user home directory/.ssh/id_rsa. So it seems it's a ssh access issue. What's bad - there are no records about the problem in jenkins log. Now I have the second case. The same symptoms but on JClouds provided slaves and I wonder what should I do. 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] [ssh-slaves] (JENKINS-10641) After Oracle Java 7 release unable to install JDKs on new Slaves
Alexander Uvizhev commented on JENKINS-10641 After Oracle Java 7 release unable to install JDKs on new Slaves I've got almost the same with Jenkins ver. 1.570: [08/07/14 12:07:24] [SSH] Checking java version of /tmp/jenkins/jdk/bin/java Couldn't figure out the Java version of /tmp/jenkins/jdk/bin/java bash: /tmp/jenkins/jdk/bin/java: No such file or directory Linux tmp-uvizhe 3.2.0-67-virtual #101-Ubuntu SMP Tue Jul 15 18:25:18 UTC 2014 i686 athlon i386 GNU/Linux Installing JDK jdk-6u45-oth-JPR@CDS-CDS_Developer Downloading JDK from http://download.oracle.com/otn/java/jdk/6u45-b06/jdk-6u45-linux-i586.bin Oracle now requires Oracle account to download previous versions of JDK. Please specify your Oracle account username/password. hudson.util.IOException2: Could not find any known supported java version in [java, /usr/bin/java, /usr/java/default/bin/java, /usr/java/latest/bin/java, /usr/local/bin/java, /usr/local/java/bin/java, /tmp/jenkins/jdk/bin/java], and we also failed to install JDK as a fallback at hudson.plugins.sshslaves.SSHLauncher.resolveJava(SSHLauncher.java:746) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:653) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:642) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Caused by: hudson.AbortException: Unable to install JDK unless a valid Oracle account username/password is provided in the system configuration. at hudson.tools.JDKInstaller.locate(JDKInstaller.java:437) at hudson.plugins.sshslaves.SSHLauncher.attemptToInstallJDK(SSHLauncher.java:853) at hudson.plugins.sshslaves.SSHLauncher.resolveJava(SSHLauncher.java:744) ... 6 more 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-19569) Git polling builds even when includes section doesn't include the changes
Alexander Uvizhev commented on JENKINS-19569 Git polling builds even when includes section doesnt include the changes I got a similar issue. Set only included region (like mydir/.*) but builds are triggered on every change. 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-20569) Polling with excluded regions don't prevent job triggered
Alexander Uvizhev commented on JENKINS-20569 Polling with excluded regions dont prevent job triggered So Included/Excluded Regions doesn't work without "Force polling using workspace", is it? If so, should the first option at least mention it or even forcibly enable the second one? 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-17614) Jenkins triggers builds on git SCM changes, but nothing changed
Alexander Uvizhev commented on JENKINS-17614 Jenkins triggers builds on git SCM changes, but nothing changed I don't understand how a job which does not poll could trigger on SCM changes. Mark, that was a reason why I created this issue. However it doesn't occur in my Jenkins anymore. I believe it has disappeared with other strange things when I turned Maven Integration Plugin on (I've disabled it shortly after I installed Jenkins). 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] [git] (JENKINS-17614) Jenkins triggers builds on SCM changes although not configured
Alexander Uvizhev created JENKINS-17614 Jenkins triggers builds on SCM changes although not configured Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 15/Apr/13 2:13 PM Description: Hi, Recently I've upgraded Jenkins to ver 1.508 and many plugins (including Jenkins GIT plugin from 1.1.25 to 1.3.0) and since that time I got a lot of my jobs using Git SCM running very frequently without any reason. None of my jobs using "Poll SCM" in "Build Triggers". But I see them running with build cause "Started by an SCM change" though very often there are no changes at all. And Polling Log is always empty. Project: Jenkins Priority: Major Reporter: Alexander Uvizhev 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.
