[JIRA] (JENKINS-42603) Additional Build arguments not working in Cloudbees Docker build and publish plugin 1.3.2
Title: Message Title Saranya U updated an issue Jenkins / JENKINS-42603 Additional Build arguments not working in Cloudbees Docker build and publish plugin 1.3.2 Change By: Saranya U Environment: Jenkins version - 2.32.3CloudBees Docker Build and Publish plugin version- 1.3.2Operating System - Ubuntu 14.04Java - 1.8 Docker - 1.13.0 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-42603) Additional Build arguments not working in Cloudbees Docker build and publish plugin 1.3.2
Title: Message Title Saranya U commented on JENKINS-42603 Re: Additional Build arguments not working in Cloudbees Docker build and publish plugin 1.3.2 Docker version is 1.13.0 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-42603) Additional Build arguments not working in Cloudbees Docker build and publish plugin 1.3.2
Title: Message Title Saranya U updated an issue Jenkins / JENKINS-42603 Additional Build arguments not working in Cloudbees Docker build and publish plugin 1.3.2 Change By: Saranya U Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-42603) Additional Build arguments not working in Cloudbees Docker build and publish plugin 1.3.2
Title: Message Title Saranya U updated an issue Jenkins / JENKINS-42603 Additional Build arguments not working in Cloudbees Docker build and publish plugin 1.3.2 Change By: Saranya U Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-42603) Additional Build arguments not working in Cloudbees Docker build and publish plugin 1.3.2
Title: Message Title Saranya U created an issue Jenkins / JENKINS-42603 Additional Build arguments not working in Cloudbees Docker build and publish plugin 1.3.2 Issue Type: Bug Assignee: Carlos Sanchez Components: docker-build-publish-plugin Created: 2017/Mar/09 6:44 AM Environment: Jenkins version - 2.32.3 CloudBees Docker Build and Publish plugin version- 1.3.2 Operating System - Ubuntu 14.04 Java - 1.8 Labels: plugin Priority: Minor Reporter: Saranya U In the Build step of Docker build and publish, there is an option to provide Additional build arguments but when I give --build-arg https_proxy="http://some.proxy:port" It shows following error [Docker_test] $ docker build --build-arg https_proxy=http://some.proxy:port -t image/ob:latest --pull=true /var/lib/jenkins/workspace/Docker_test flag provided but not defined: --build-arg See 'docker build --help'. Build step 'Docker Build and Publish' marked build as failure Finished: FAILURE But when executed in shell command, the above mentioned command works fine
[JIRA] (JENKINS-40668) The Server rejected the connection: None of the protocols were accepted
Title: Message Title Saranya U created an issue Jenkins / JENKINS-40668 The Server rejected the connection: None of the protocols were accepted Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Dec/26 5:54 AM Environment: Jenkins version 2.7.4 installed as master on Ubuntu 14.04 Priority: Blocker Reporter: Saranya U Dec 26, 2016 11:12:07 AM hudson.remoting.jnlp.Main createEngine INFO: Setting up slave: PCNew Dec 26, 2016 11:12:07 AM hudson.remoting.jnlp.Main$CuiListener INFO: Jenkins agent is running in headless mode. Dec 26, 2016 11:12:07 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Locating server among https://myserver/jenkins/, http://myserver:8080/jenkins/ Dec 26, 2016 11:12:07 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Handshaking Dec 26, 2016 11:12:07 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Connecting to myserver:56029 Dec 26, 2016 11:12:07 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Trying protocol: JNLP3-connect Dec 26, 2016 11:12:07 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Server didn't accept the handshake: Unknown protocol:Protocol:JNLP3-connec t Dec 26, 2016 11:12:07 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Connecting to myserver:56029 Dec 26, 2016 11:12:07 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Trying protocol: JNLP2-connect Dec 26, 2016 11:12:07 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Server didn't accept the handshake: PCNew is already connected to this mas ter. Rejecting this connection. Dec 26, 2016 11:12:07 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Connecting to myserver:56029 Dec 26, 2016 11:12:07 AM hudson.remoting.jnlp.Main$CuiListener status INFO: Trying protocol: JNLP-connect Dec 26, 2016 11:12:07 AM
