[JIRA] (JENKINS-46468) "no such computer" error occurs during SCM Pulling
Title: Message Title Balázs Hámorszky commented on JENKINS-46468 Re: "no such computer" error occurs during SCM Pulling allowing master nodes and putting this in the pipeline solved this for me: node('master') { checkout scm } Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.184739.1503686001000.6028.1572522480277%40Atlassian.JIRA.
[JIRA] (JENKINS-59810) Kubernetes Plugin fails with PVC error from 1.19.2 onwards
Title: Message Title B aldey updated an issue Jenkins / JENKINS-59810 Kubernetes Plugin fails with PVC error from 1.19.2 onwards Change By: B aldey Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.202541.157126394.5553.1572459900165%40Atlassian.JIRA.
[JIRA] (JENKINS-59810) Kubernetes Plugin fails with PVC error from 1.19.2 onwards
Title: Message Title B aldey created an issue Jenkins / JENKINS-59810 Kubernetes Plugin fails with PVC error from 1.19.2 onwards Issue Type: Bug Assignee: Unassigned Components: kubernetes-plugin Created: 2019-10-16 22:12 Environment: kubernetes plugin 1.19.2 to 1.20.0 kubernetes 1.14.6 Jenkins ver. 2.190.1 Labels: kubernetes-plugin Priority: Minor Reporter: B aldey We are running jenkins within kubernetes, we find that if we upgrade the kubernetes plugin to 1.19.2 or above we get the following pvc based error when jenkins master tries to spawn worker pods, even though we do not specify any PVC within our pod templates: io.fabric8.kubernetes.client.KubernetesClientException: Failure executing: POST at: https://kubernetes.default/api/v1/namespaces/jenkins/persistentvolumeclaims. Message: PersistentVolumeClaim in version "v1" cannot be handled as a PersistentVolumeClaim: v1.PersistentVolumeClaim.Spec: v1.PersistentVolumeClaimSpec.StorageClassName: Resources: v1.ResourceRequirements.Requests: unmarshalerDecoder: quantities must match the regular _expression_ '([+-]?[0-9.])([eEinumkKMGTP][-+]?[0-9])$', error found in #10 byte of ...|torage":""}},"storag|..., bigger context ...|,"resources":{"limits":{},"requests":{"storage":""}},"storageClassName":""}}| Received status: Status(apiVersion=v1, code=400, details=null, kind=Status, message=PersistentVolumeClaim in version "v1" cannot be handled as a PersistentVolumeClaim: v1.PersistentVolumeClaim.Spec: v1.PersistentVolumeClaimSpec.StorageClassName: Resources: v1.ResourceRequirements.Requests: unmarshalerDecoder:
[JIRA] [pollscm] (JENKINS-17966) pollscm does not error when ssh auth cannot establish
Brian Buchalter created JENKINS-17966 pollscm does not error when ssh auth cannot establish Issue Type: Bug Affects Versions: current Assignee: Vincent Latombe Components: pollscm Created: 15/May/13 3:47 PM Description: When using Github SCM over SSH with polling, you must manually go into the work space and initiate the first "git fetch" so that the host is identified. It would be nice of the polling log captured this error to report to the user. Project: Jenkins Priority: Minor Reporter: Brian Buchalter 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.