[JIRA] (JENKINS-59128) hudson.model.UpdateCenter.never = true not working
Title: Message Title Jeroen Wolff created an issue Jenkins / JENKINS-59128 hudson.model.UpdateCenter.never = true not working Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-08-28 18:34 Priority: Minor Reporter: Jeroen Wolff When is start Jenkins there is alway a connection made to the UpdateCentre. Even when i set hudson.model.UpdateCenter.never to true I have no internet so there is always a timeout in the log. Looks like a scheduled action which i cannot stop. INFO: The attempt #1 to do the action check updates server failed with an allowed exception: java.net.SocketTimeoutException: connect timed out at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) at java.net.Socket.connect(Socket.java:589) at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:666) at sun.net.NetworkClient.doConnect(NetworkClient.java:175) at sun.net.www.http.HttpClient.openServer(HttpClient.java:463) at sun.net.www.http.HttpClient.openServer(HttpClient.java:558) at sun.net.www.protocol.https.HttpsClient.(HttpsClient.java:264) at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:367) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:191) at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1162) at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1056) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:177) at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1570) at sun.net.www.protocol.http.HttpURLConnection.getInputStre
[JIRA] (JENKINS-40838) kubernetes plugin 0.10 fails root directory not writeable
Title: Message Title Jeroen Wolff commented on JENKINS-40838 Re: kubernetes plugin 0.10 fails root directory not writeable is working fine with the latest version Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.177552.1483623371000.13415.1563314220575%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40838) kubernetes plugin 0.10 fails root directory not writeable
Title: Message Title Jeroen Wolff closed an issue as Fixed Jenkins / JENKINS-40838 kubernetes plugin 0.10 fails root directory not writeable Change By: Jeroen Wolff Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.177552.1483623371000.13416.1563314220589%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40838) kubernetes plugin 0.10 fails root directory not writeable
Title: Message Title Jeroen Wolff created an issue Jenkins / JENKINS-40838 kubernetes plugin 0.10 fails root directory not writeable Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2017/Jan/05 1:36 PM Priority: Minor Reporter: Jeroen Wolff When i upgrade from 0.9 to 0.10 my slave container is not working anymore Root directory not writable log: Downloading http://172.30.123.108:80/jnlpJars/remoting.jar ... Running java -cp /home/jenkins/remoting.jar hudson.remoting.jnlp.Main -headless -url http://172.30.123.108:80 -tunnel 172.30.76.68:5 2f575767184b7cf61c0d60d8c9e1eafdd4f99e8914115f8ca856df32ecf8051f maven-7c82ab211e81 Dec 30, 2016 9:54:13 PM hudson.remoting.jnlp.Main createEngine INFO: Setting up slave: maven-7c82ab211e81 Dec 30, 2016 9:54:13 PM hudson.remoting.jnlp.Main$CuiListener INFO: Jenkins agent is running in headless mode. Exception in thread "main" java.lang.RuntimeException: Root directory not writable at hudson.remoting.FileSystemJarCache.(FileSystemJarCache.java:44) at hudson.remoting.Engine.(Engine.java:148) at hudson.remoting.jnlp.Main.createEngine(Main.java:168) at hudson.remoting.jnlp.Main.main(Main.java:152) at hudson.remoting.jnlp.Main._main(Main.java:148) at hudson.remoting.jnlp.Main.main(Main.java:114)
[JIRA] (JENKINS-40277) Allow Jenkins to see k8s nodes as available executor
Title: Message Title Jeroen Wolff commented on JENKINS-40277 Re: Allow Jenkins to see k8s nodes as available executor No i had not. Now i've tested it and works great thanks! 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-40277) Allow Jenkins to see k8s nodes as available executor
Title: Message Title
Jeroen Wolff created an issue
Jenkins / JENKINS-40277
Allow Jenkins to see k8s nodes as available executor
Issue Type:
Improvement
Assignee:
Carlos Sanchez
Components:
kubernetes-plugin
Created:
2016/Dec/07 12:35 PM
Priority:
Minor
Reporter:
Jeroen Wolff
When i have 5 executors available and in my script i make use of a maven node like: node('maven') { [code] } When i fire 5 build jobs, they are not build in parallel. It looks like Jenkins is thinking that there is only 1 node available all the time. Instead with kube you could start multiple nodes at the same time. I would like to see that Jenkins is always starting to use a node one kube instead of only one at the time.
Add Comment
[JIRA] (JENKINS-40132) Persistent Volume Claim properties are not shown
Title: Message Title Jeroen Wolff updated an issue Jenkins / JENKINS-40132 Persistent Volume Claim properties are not shown Change By: Jeroen Wolff Attachment: PastedGraphic-1.tiff 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-40132) Persistent Volume Claim properties are not shown
Title: Message Title Jeroen Wolff updated an issue Jenkins / JENKINS-40132 Persistent Volume Claim properties are not shown Change By: Jeroen Wolff Attachment: PersistentClaim.png 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-40132) Persistent Volume Claim properties are not shown
Title: Message Title Jeroen Wolff updated an issue Jenkins / JENKINS-40132 Persistent Volume Claim properties are not shown Change By: Jeroen Wolff Attachment: PastedGraphic-1.tiff 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-40132) Persistent Volume Claim properties are not shown
Title: Message Title Jeroen Wolff created an issue Jenkins / JENKINS-40132 Persistent Volume Claim properties are not shown Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2016/Nov/30 9:18 PM Environment: Jenkins 2.19.3 Priority: Minor Reporter: Jeroen Wolff Add an Persistent Volume Claim via Jenkins configuration. The options (claimName, mountPath, readOnly) are not shown in Jenkins 2.19.3 Add Comment
[JIRA] (JENKINS-39566) Auto configure Kubernetes Jenkins plugin
Title: Message Title Jeroen Wolff edited a comment on JENKINS-39566 Re: Auto configure Kubernetes Jenkins plugin Take a look at how Ben Parees is doing it with his slave images. A nice script at [kube-slave-common.sh title |https://github.com/openshift/jenkins/blob/master/2/contrib/jenkins/kube-slave-common.sh] 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-39566) Auto configure Kubernetes Jenkins plugin
Title: Message Title Jeroen Wolff commented on JENKINS-39566 Re: Auto configure Kubernetes Jenkins plugin Take a look at how Ben Parees is doing it with his slave images. A nice script at kube-slave-common.sh title 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.
