[JIRA] (JENKINS-55082) No @DataBoundConstructor on io.jenkins.jenkinsfile.runner.FileSystemSCM
Title: Message Title David Currie created an issue Jenkins / JENKINS-55082 No @DataBoundConstructor on io.jenkins.jenkinsfile.runner.FileSystemSCM Issue Type: Bug Assignee: Oleg Nenashev Components: jenkinsfile-runner Created: 2018-12-07 14:34 Environment: Jenkins X: jx 1.3.620 jenkins x platform 0.0.3007 Priority: Minor Reporter: David Currie Jenkins X builds contain the following error on a checkout scm: 31.426 [id=67] WARNING o.j.plugins.workflow.cps.DSL#invokeStep: Error storing the arguments for step: checkout org.kohsuke.stapler.NoStaplerConstructorException: There's no @DataBoundConstructor on any constructor of class io.jenkins.jenkinsfile.runner.FileSystemSCM at org.kohsuke.stapler.ClassDescriptor.loadConstructorParamNames(ClassDescriptor.java:265) at org.jenkinsci.plugins.structs.describable.DescribableModel.(DescribableModel.java:144) at org.jenkinsci.plugins.structs.describable.DescribableModel.of(DescribableModel.java:114) at org.jenkinsci.plugins.workflow.cps.actions.ArgumentsActionImpl.sanitizeObjectAndRecordMutation(ArgumentsActionImpl.java:294) at org.jenkinsci.plugins.workflow.cps.actions.ArgumentsActionImpl.sanitizeMapAndRecordMutation(ArgumentsActionImpl.java:386) at org.jenkinsci.plugins.workflow.cps.actions.ArgumentsActionImpl.(ArgumentsActionImpl.java:74) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:245) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:178) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122) at
[JIRA] (JENKINS-54512) can not change workspace in k8s pipeline
Title: Message Title David Currie commented on JENKINS-54512 Re: can not change workspace in k8s pipeline Why not just change your GOPATH then? 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title David Currie commented on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted You can't expect to be able to just swap out the Docker socket for a containerd socket and have that work. Even setting that aside, containerd doesn't even have the concept of building images. I've been out of the loop a bit with IKS but I suspect the path of least resistance here is to have Jenkins use the IBM Container Registry to build your Docker images i.e. via ibmcloud cr build. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title
David Currie edited a comment on JENKINS-53297
Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted
Is that even if you remove the \ { { hostPathVolume} } from the \ { { podTemplate} } ? My assumption was that the slave pod was failing to start because it couldn't satisfy the requested mount.
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title
David Currie commented on JENKINS-53297
Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted
Is that even if you remove the {hostPathVolume} from the {podTemplate}? My assumption was that the slave pod was failing to start because it couldn't satisfy the requested mount.
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title
David Currie updated an issue
Jenkins / JENKINS-53297
Kubernetes v1.11 - ChannelClosed after job delaying aborted
Change By:
David Currie
I've Jenkins running on Kubernetes Cluster (Bluemix IKS).I am using the kubernetes plugin to create dynamic agents.The jenkins connection with agent is made in the standard way: - Jenkins URL: jenkins:8080- Jenkins Tunnel: jenkins-agent:5 When i start a job, the agent connect with Jenkins master successfully. But he keeps long time and not execute pipeline steps. Agent logs: {code:java}Warning: JnlpProtocol3 is disabled by default, use JNLP_PROTOCOL_OPTS to alter the behaviorWarning: JnlpProtocol3 is disabled by default, use JNLP_PROTOCOL_OPTS to alter the behaviorAug 29, 2018 12:07:02 AM hudson.remoting.jnlp.Main createEngineINFO: Setting up agent: jenkins-slave-n39mq-9zgzzAug 29, 2018 12:07:03 AM hudson.remoting.jnlp.Main$CuiListener INFO: Jenkins agent is running in headless mode.Aug 29, 2018 12:07:03 AM hudson.remoting.Engine startEngineINFO: Using Remoting version: 3.23Aug 29, 2018 12:07:03 AM hudson.remoting.Engine startEngineWARNING: No Working Directory. Using the legacy JAR Cache location: /home/jenkins/.jenkins/cache/jarsAug 29, 2018 12:07:03 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Locating server among [http://jenkins:8080/]Aug 29, 2018 12:07:03 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]Aug 29, 2018 12:07:03 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFO: Remoting TCP connection tunneling is enabled. Skipping the TCP Agent Listener Port availability checkAug 29, 2018 12:07:03 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Agent discovery successful Agent address: jenkins-agent Agent port: 5 Identity: bb:d3:5f:09:02:5c:56:70:04:7f:8f:72:f5:bd:23:79Aug 29, 2018 12:07:03 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: HandshakingAug 29, 2018 12:07:03 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Connecting to jenkins-agent:5Aug 29, 2018 12:07:03 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Trying protocol: JNLP4-connectAug 29, 2018 12:07:03 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Remote identity confirmed: bb:d3:5f:09:02:5c:56:70:04:7f:8f:72:f5:bd:23:79Aug 29, 2018 12:07:04 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: ConnectedAug 29, 2018 12:12:09 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesSlave$SlaveDisconnector callINFO: Disabled slave engine reconnects.Aug 29, 2018 12:12:09 AM hudson.util.ProcessTree getWARNING: Error while determining if vetoers existhudson.remoting.RequestAbortedException: hudson.remoting.ChannelClosedException: Channel "unknown": Protocol stack cannot write data anymore. ChannelApplicationLayer reports that the NIO Channel is closed at hudson.remoting.Request.abort(Request.java:340) at hudson.remoting.Channel.terminate(Channel.java:1038) at hudson.remoting.Channel.close(Channel.java:1439)
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title David Currie commented on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted Is that Jenkinsfile just an example or what you're actually trying to achieve? You shouldn't need a Docker socket in order to use helm. That is not to say that this isn't a problem in other scenarios e.g. when trying to use the daemon on the Kubernetes node to perform Docker builds. In that case, you could look at using kaniko or fall back to Docker-in-Docker. 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50772) Content type not set reasonably
Title: Message Title David Currie commented on JENKINS-50772 Re: Content type not set reasonably My reading is the same as Jarrad Whitaker. The S3 API indicates that the default Content-Type on a PUT is binary/octet-stream unless you specify otherwise. 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. For more options, visit https://groups.google.com/d/optout.
