Re: Kubernetes-Plugin BadRequest container name must be specified
1. I was using the external name rather than the internal (cluster.local) DNS name in the Kubernetes Cloud Configuration in Jenkins 2. Even when I switched it appears it's because the port is necessary (http://jenkins.jenkins.svc.cluster.local:443) which I found in open issue (https://issues.jenkins-ci.org/browse/JENKINS-48368) 3. If Jenkins wasn't running within a Kubernetes cluster but you wanted to leverage the slaves/agents to be run on one then I'm guessing a slave secret would need to be made available. Can documentation for #2 and #3 be made/updated for future? Thanks On Monday, January 22, 2018 at 3:01:41 PM UTC-5, Chris Denneen wrote: > > I've installed latest LTS of jenkins and installed latest > kubernetes-plugin. > > I've created 2 pipeline jobs to test: > > pod-golang from here ( > https://kumorilabs.com/blog/k8s-6-integrating-jenkins-kubernetes/) > and one from Carlos Sanchez blog here ( > https://blog.csanchez.org/2016/10/25/jenkins-kubernetes-plugin-0-9-released/ > ) > > Both pods create with the following logs and loop: > > work/capdev-kubernetes » kubectl logs jenkins-slave-1kl4v-flv53 > Error from server (BadRequest): a container name must be specified for pod > jenkins-slave-1kl4v-flv53, choose one of: [golang jnlp] > > work/capdev-kubernetes » kubectl logs jenkins-slave-pwcwz-2k20s > Error from server (BadRequest): a container name must be specified for pod > jenkins-slave-pwcwz-2k20s, choose one of: [maven golang jnlp] > > > Is there something else that needs to be done in order to get these to > work? > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/01214aa2-964c-4819-99e8-75e8c712b9b1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Kubernetes-Plugin BadRequest container name must be specified
jnlp:
Warning: JnlpProtocol3 is disabled by default, use JNLP_PROTOCOL_OPTS to
alter the behavior
Warning: SECRET is defined twice in command-line arguments and the
environment variable
Warning: AGENT_NAME is defined twice in command-line arguments and the
environment variable
Jan 22, 2018 9:27:05 PM hudson.remoting.jnlp.Main createEngine
INFO: Setting up agent: golang-d4xmn-qk7g5
Jan 22, 2018 9:27:05 PM hudson.remoting.jnlp.Main$CuiListener
INFO: Jenkins agent is running in headless mode.
Jan 22, 2018 9:27:05 PM hudson.remoting.Engine startEngine
WARNING: No Working Directory. Using the legacy JAR Cache location:
/home/jenkins/.jenkins/cache/jars
Jan 22, 2018 9:27:05 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Locating server among [https://jenkins.k8s.example.com/]
Jan 22, 2018 9:27:05 PM
org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve
INFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]
Jan 22, 2018 9:27:05 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Agent discovery successful
Agent address: jenkins.k8s.example.com
Agent port:5
Identity: 67:79:2e:b1:ec:6e:88:d4:d3:36:0a:8a:60:62:3c:40
Jan 22, 2018 9:27:05 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Handshaking
Jan 22, 2018 9:27:05 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Connecting to jenkins.k8s.example.com:5
Jan 22, 2018 9:27:05 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Trying protocol: JNLP4-connect
Jan 22, 2018 9:27:05 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Protocol JNLP4-connect encountered an unexpected exception
java.util.concurrent.ExecutionException:
org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException: Connection
closed before acknowledgement sent
at org.jenkinsci.remoting.util.SettableFuture.get(SettableFuture.java:223)
at hudson.remoting.Engine.innerRun(Engine.java:609)
at hudson.remoting.Engine.run(Engine.java:469)
Caused by: org.jenkinsci.remoting.protocol.impl.ConnectionRefusalException:
Connection closed before acknowledgement sent
at
org.jenkinsci.remoting.protocol.impl.AckFilterLayer.onRecvClosed(AckFilterLayer.java:280)
at
org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecvClosed(ProtocolStack.java:832)
at
org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154)
at
org.jenkinsci.remoting.protocol.impl.BIONetworkLayer.access$1500(BIONetworkLayer.java:48)
at
org.jenkinsci.remoting.protocol.impl.BIONetworkLayer$Reader.run(BIONetworkLayer.java:247)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at hudson.remoting.Engine$1$1.run(Engine.java:94)
at java.lang.Thread.run(Thread.java:748)
Jan 22, 2018 9:27:05 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Connecting to jenkins.k8s.example.com:5
Jan 22, 2018 9:27:05 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Server reports protocol JNLP4-plaintext not supported, skipping
Jan 22, 2018 9:27:05 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Protocol JNLP3-connect is not enabled, skipping
Jan 22, 2018 9:27:05 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Server reports protocol JNLP2-connect not supported, skipping
Jan 22, 2018 9:27:05 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Server reports protocol JNLP-connect not supported, skipping
Jan 22, 2018 9:27:05 PM hudson.remoting.jnlp.Main$CuiListener error
SEVERE: The server rejected the connection: None of the protocols were
accepted
java.lang.Exception: The server rejected the connection: None of the
protocols were accepted
at hudson.remoting.Engine.onConnectionRejected(Engine.java:670)
at hudson.remoting.Engine.innerRun(Engine.java:634)
at hudson.remoting.Engine.run(Engine.java:469)
work/capdev-kubernetes » kubectl logs golang-d4xmn-qk7g5 golang
failed to get container status {"docker"
"88c88f113b96b5424389981e06e4b4336c442b34d5cff14fffb8f005cbce9058"}: rpc
error: code = Unknown desc = Error: No such container:
88c88f113b96b542438998work/capdev-kubernetes » kubectl logs
golang-d4xmn-qk7g5 golang
failed to get container status {"docker"
"88c88f113b96b5424389981e06e4b4336c442b34d5cff14fffb8f005cbce9058"}: rpc
error: code = Unknown desc = Error: No such container:
88c88f113b96b542438998work/capdev-kubernetes » kubectl logs
golang-d4xmn-qk7g5 golang
failed to get container status {"docker"
"88c88f113b96b5424389981e06e4b4336c442b34d5cff14fffb8f005cbce9058"}: rpc
error: code = Unknown desc = Error: No such container:
88c88f113b96b542438998work/capdev-kubernetes » kubectl logs
golang-d4xmn-qk7g5 golang
failed to get container status {"docker"
"88c88f113b96b5424389981e06e4b4336c442b34d5cff14fffb8f005cbce9058"}: rpc
error: code = Unknown desc = Error: No such container:
88c88f113b96b542438998work/capdev-kubernetes » kubectl logs
golang-d4xmn-qk7g5 jnlp
Warning: JnlpProtocol3 is disabled
Re: Webhooks in hosted gitlab + local jenkins setup
Why didn't DDNS work? On Monday, January 22, 2018 at 1:42:45 PM UTC-5, Lorem Ipsum wrote: > > Hello, > > I've got a question and a possible answer but since I'm new to Jenkins and > it's plugins maybe there is an easier way to do the thing I'm trying to > accomplish. > > First of my current setup is the following: > > - Gitlab hosted on a server > - Jenkins on premise with dynamic IP and hard to open up a port > > Since I understood by now that polling is a CI anti-pattern I'd very much > like to use webhooks to trigger Jenkins builds but of course I won't be > able to set this up with webhook posting to localhost. > So I've thought of posting to an intermediary script (eg. node.js) running > on a external server with static IP which would receive all of the webhooks > and which Jenkins would be connected to with a client via a socket for > example, effectively waiting for incoming data. Upon new data it would > trigger new Jenkins job locally, expectedly immediately after the > intermediary receives the payload. > > I know it's a bit odd way around but opening up a port is a bigger > difficulty in my setup than actually deploying the above. Also hosting > Jenkins on the mentioned server is not an option for me as I want to run > builds and tests on actual hardware in some cases. > > So my question would be if maybe there is some already existing solution > for this? Initially I've tried with DDNS but it didn't do the job > unfortunately. > I've been looking for topics from people with similar experiences but > haven't found anything. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/5b943dde-296f-49c1-93aa-987d3dc37091%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Kubernetes-Plugin BadRequest container name must be specified
I've installed latest LTS of jenkins and installed latest kubernetes-plugin. I've created 2 pipeline jobs to test: pod-golang from here ( https://kumorilabs.com/blog/k8s-6-integrating-jenkins-kubernetes/) and one from Carlos Sanchez blog here ( https://blog.csanchez.org/2016/10/25/jenkins-kubernetes-plugin-0-9-released/ ) Both pods create with the following logs and loop: work/capdev-kubernetes » kubectl logs jenkins-slave-1kl4v-flv53 Error from server (BadRequest): a container name must be specified for pod jenkins-slave-1kl4v-flv53, choose one of: [golang jnlp] work/capdev-kubernetes » kubectl logs jenkins-slave-pwcwz-2k20s Error from server (BadRequest): a container name must be specified for pod jenkins-slave-pwcwz-2k20s, choose one of: [maven golang jnlp] Is there something else that needs to be done in order to get these to work? -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAP0Su%2BKLQCYLtMb21%3DvKzRJAfUPZnMkncGpmp9D1zoB%2BAeh9qA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: Multi Configuration Job Jenkinsfile
Thanks R Tyler... I guess my bigger question is how to migrate away from Freestyle and Multi-Config type jobs into Pipeline/Groovy style jobs. Not sure there is a way to configure the build triggers or post build actions. For example kick off build when PR happens... I know these are checkboxes in UI but in moving to "config as code" is there a way to do this in the Jenkinsfile? Do you recommend saving the xml off and using jenkinsci-puppet module? or something like JJB? On Thursday, February 23, 2017 at 3:48:01 PM UTC-5, R Tyler Croy wrote: > > (replies inline) > > On Thu, 23 Feb 2017, Chris Denneen wrote: > > > Sathish? What are you referring to here? > > This is UI configuration. I've had this for a while. > > I'm looking for Jenkinsfile equivalent. > > > There is no such thing as a "Multiconfiguration Pipeline" as such in > Pipeline. > You might find the use of the parallel() step to be helpful here however: > > https://jenkins.io/doc/book/pipeline/jenkinsfile/#advanced-scripted-pipeline > > > - R. Tyler Croy > > -- > Code: <https://github.com/rtyler> > Chatter: <https://twitter.com/agentdero> > xmpp: rty...@jabber.org > > % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F > -- > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/3d152e69-519f-4f32-8245-8dd462bef660%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Multi Configuration Job Jenkinsfile
Sathish? What are you referring to here? This is UI configuration. I've had this for a while. I'm looking for Jenkinsfile equivalent. Thanks On Wednesday, February 22, 2017 at 9:58:31 PM UTC-5, sathish g wrote: > > > > On Sunday, February 19, 2017 at 8:17:29 PM UTC+5:30, Chris Denneen wrote: >> >> Anyone have any suggestions? >> Trying to run a multi configuration job for different RUBY_VERSION and >> PUPPET_VERSION. Also this job needs to pin the jobs on a particular slave >> with slave axis > > > >> Use multi configuration job with Configuration Matrix > > > > https://www.safaribooksonline.com/library/view/jenkins-the-definitive/9781449311155/ch10s04.html > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/df99f3e6-629b-4f85-9f5b-92f29c8e1a28%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Multi Configuration Job Jenkinsfile
Anyone have any suggestions? Trying to run a multi configuration job for different RUBY_VERSION and PUPPET_VERSION. Also this job needs to pin the jobs on a particular slave with slave axis -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/3567ebf5-406c-46f0-8f15-7893bd1e90d7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Multi Configuration Job Jenkinsfile
I'm looking for example to replace existing Multi Configuration Job with Jenkinsfile that handles X Y axis mapping. Also needs to support Matrix Configuration (so which X:Y mappings to do) and Slave label to run that job on. In the multi configuration job even if called from pipeline on node X... when it runs the child jobs it runs them on random nodes without a Slave Axis. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/ea3da699-0199-42f4-b3cc-5aba19a370b7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
