[JIRA] (JENKINS-49077) pipeline checkout step does not perform retries
Title: Message Title
Quentin Nerden edited a comment on JENKINS-49077
Re: pipeline checkout step does not perform retries
[~jekeller]"However, I'm unable to do this for the checkout step that occurs as part of fetching the pipeline code."You can skip that default checkout step with the option "skipDefaultCheckout()", like this: {code:java} agent { label 'docker:creator' } options { skipDefaultCheckout() }{code}
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-49077) pipeline checkout step does not perform retries
Title: Message Title
Quentin Nerden commented on JENKINS-49077
Re: pipeline checkout step does not perform retries
Jacob Keller "However, I'm unable to do this for the checkout step that occurs as part of fetching the pipeline code." You can skip that default checkout step with the option "skipDefaultCheckout()", like this:
agent { label 'docker:creator' }
options { skipDefaultCheckout() }
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-49037) git clone does not retry if connection aborted
Title: Message Title Quentin Nerden commented on JENKINS-49037 Re: git clone does not retry if connection aborted This issue is the same as https://issues.jenkins-ci.org/browse/JENKINS-49077?jql=project%20%3D%20JENKINS%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20component%20%3D%20workflow-cps-plugin 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-49037) git clone does not retry if connection aborted
Title: Message Title Quentin Nerden assigned an issue to Quentin Nerden Jenkins / JENKINS-49037 git clone does not retry if connection aborted Change By: Quentin Nerden Assignee: Quentin Nerden 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-13493) GitPlugin should garbage collect
Title: Message Title
Quentin Nerden commented on JENKINS-13493
Re: GitPlugin should garbage collect
Is this still in review? We just had a issue where the .git folder had so much leftover in it that it started to give problems in the Jenkins master. Running {{git gc --prune=now }} manually solved it. An option to have this done by Jenkins would be nice.
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-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Quentin Nerden edited a comment on JENKINS-51132 Re: workflow blocks on cps.CpsFlowExecution.getCurrentHeads Confirmed, 2.52 has issues and 2.49 works without deadlocks. Is there a new bug we could subscribe to? [~svanoort] Or can we reopen this bug? 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-51132) workflow blocks on cps.CpsFlowExecution.getCurrentHeads
Title: Message Title Quentin Nerden commented on JENKINS-51132 Re: workflow blocks on cps.CpsFlowExecution.getCurrentHeads Confirmed, 2.52 has issues and 2.49 works without deadlocks. Is there a new bug we could subscribe to? Or can we reopen this bug? 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] [docker-build-publish-plugin] (JENKINS-29085) Allow to use the docker build --file option when building an image
Title: Message Title Quentin Nerden commented on JENKINS-29085 Re: Allow to use the docker build --file option when building an image Looking at the screenshot under "How to use" in the jenkins wiki: https://wiki.jenkins-ci.org/display/JENKINS/CloudBees+Docker+Build+and+Publish+plugin shows a textbox called Build Context. This seems to be this feature. Was it part of the plugin and then removed? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [hipchat-plugin] (JENKINS-22723) Cannot pass hipchat room number as a parameter to a job
Title: Message Title
Quentin Nerden commented on JENKINS-22723
Re: Cannot pass hipchat room number as a parameter to a job
Same for us, we'd like to be able to use a hipchat room Jenkins parameter to set the room to notify. I had created a bug directly in Github: https://github.com/jenkinsci/hipchat-plugin/issues/44 but here seems to be the correct place.
I set the value of the parameter when calling the job. In the Jenkins job config:
Checkbox: This build is parameterized is checked, Text parameter HIPCHATROOM added, with value 1332745, In Hipchat Noficiations, Project room is set to $ {HIPCHATROOM}
There is no Hipchat notifications when the build starts/fails/suceeds/etc.
I DO get a notification if Project room is set to 1332745 in In Hipchat Noficiations.
This is with version 0.1.9 of the plugin. (Jenkins ver. 1.617)
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [hipchat-plugin] (JENKINS-22723) Cannot pass hipchat room number as a parameter to a job
Title: Message Title
Quentin Nerden edited a comment on JENKINS-22723
Re: Cannot pass hipchat room number as a parameter to a job
Sameforus,we'dliketobeabletouseahipchatroomJenkinsparametertosettheroomtonotify.IhadcreatedabugdirectlyinGithub:https://github.com/jenkinsci/hipchat-plugin/issues/44buthere inJIRA seemstobethecorrectplace.Isetthevalueoftheparameterwhencallingthejob.IntheJenkinsjobconfig:Checkbox:Thisbuildisparameterizedischecked,TextparameterHIPCHATROOMadded,withvalue1332745,InHipchatNoficiations,Projectroomissetto${HIPCHATROOM}ThereisnoHipchatnotificationswhenthebuildstarts/fails/suceeds/etc.IDOgetanotificationifProjectroomissetto1332745inInHipchatNoficiations.Thisiswithversion0.1.9oftheplugin.(Jenkinsver.1.617)
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [docker-build-publish-plugin] (JENKINS-29085) Allow to use the docker build --file option when building an image
Title: Message Title
Quentin Nerden updated an issue
Jenkins / JENKINS-29085
Allow to use the docker build --file option when building an image
Change By:
Quentin Nerden
Allowtousethedockerbuild{{--file}}optionwhenbuildinganimageWewouldliketoNOThavetheDockerfileattherootoftheproject,andhaveeverythingdockerrelatedinasubfolderdocker.Thenwewouldbuildtheimagewith{{dockerbuild-tmyrepo/myproject:v01--filedocker/Dockerfile.}}'.'isthedockercontext,meaningeventhoughtheDockerfileisinasubfolder'docker',dockercanstillaccesseverythingunder'.'(therootoftheproject).Itisnotpossibleotherwisetoaccessfoldersoutsideofthecontext,inaDockerfile(using{{ADD../scr/myfile.jar/srv/lib/ myfile.jar }},forexample.'..'isnotallowed).Soitwouldbenicetostillhavetheoption:-DirectoryDockerfileisin(equivalentof--filepath)-Dockercontext.Note:Inthecode,thisseemstobeinfunctionbuildAndTag()infile:{{src/main/java/com/cloudbees/dockerpublish/DockerBuilder.java}}{{Stringcontext=defined(getDockerfilePath())? getDockerfilePath():.; lastResult=executeCmd(dockerbuild-t+i.next() +((isNoCache())?--no-cache=true:)+ +((isForcePull())?--pull=true:)+ +context);}}Theline{{Stringcontext=defined(getDockerfilePath())}}shouldbechangedsothatDockerfilePathisnotthesameascontext.Thoseshouldbedifferentthings.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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
[JIRA] [docker-build-publish-plugin] (JENKINS-29085) Allow to use the docker build --file option when building an image
Title: Message Title
Quentin Nerden updated an issue
Jenkins / JENKINS-29085
Allow to use the docker build --file option when building an image
Change By:
Quentin Nerden
Allowtousethedockerbuild{{--file}}optionwhenbuildinganimageWewouldliketoNOThavetheDockerfileattherootoftheproject,andhaveeverythingdockerrelatedinasubfolderdocker.Thenwewouldbuildtheimagewith{{dockerbuild-tmyrepo/myproject:v01--filedocker/Dockerfile.}}'.'isthedockercontext,meaningeventhoughtheDockerfileisinasubfolder'docker',dockercanstillaccesseverythingunder'.'(therootoftheproject).Itisnotpossibleotherwisetoaccessfoldersoutsideofthecontext,inaDockerfile(using{{ADD../src/myfile.jar/srv/lib/myfile.jar}},forexample.'..'isnotallowed).Soitwouldbenicetostillhavethe option options,intheGUI :-DirectoryDockerfileisin(equivalentof--filepath)-Dockercontext.Note:Inthecode,thisseemstobeinfunctionbuildAndTag()infile:{{src/main/java/com/cloudbees/dockerpublish/DockerBuilder.java}}{{Stringcontext=defined(getDockerfilePath())? getDockerfilePath():.; lastResult=executeCmd(dockerbuild-t+i.next() +((isNoCache())?--no-cache=true:)+ +((isForcePull())?--pull=true:)+ +context);}}Theline{{Stringcontext=defined(getDockerfilePath())}}shouldbechangedsothatDockerfilePathisnotthesameascontext.Thoseshouldbedifferentthings.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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
[JIRA] [docker-build-publish-plugin] (JENKINS-29085) Allow to use the docker build --file option when building an image
Title: Message Title
Quentin Nerden updated an issue
Jenkins / JENKINS-29085
Allow to use the docker build --file option when building an image
Change By:
Quentin Nerden
Allowtousethedockerbuild{{--file}}optionwhenbuildinganimageWewouldliketoNOThavetheDockerfileattherootoftheproject,andhaveeverythingdockerrelatedinasubfolderdocker.Thenwewouldbuildtheimagewith{{dockerbuild-tmyrepo/myproject:v01--filedocker/Dockerfile.}}'.'isthedockercontext,meaningeventhoughtheDockerfileisinasubfolder'docker',dockercanstillaccesseverythingunder'.'(therootoftheproject).Itisnotpossibleotherwisetoaccessfoldersoutsideofthecontext,inaDockerfile(using{{ADD../ scr src /myfile.jar/srv/lib/myfile.jar}},forexample.'..'isnotallowed).Soitwouldbenicetostillhavetheoption:-DirectoryDockerfileisin(equivalentof--filepath)-Dockercontext.Note:Inthecode,thisseemstobeinfunctionbuildAndTag()infile:{{src/main/java/com/cloudbees/dockerpublish/DockerBuilder.java}}{{Stringcontext=defined(getDockerfilePath())? getDockerfilePath():.; lastResult=executeCmd(dockerbuild-t+i.next() +((isNoCache())?--no-cache=true:)+ +((isForcePull())?--pull=true:)+ +context);}}Theline{{Stringcontext=defined(getDockerfilePath())}}shouldbechangedsothatDockerfilePathisnotthesameascontext.Thoseshouldbedifferentthings.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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,
[JIRA] [docker-build-publish-plugin] (JENKINS-29085) Allow to use the docker build --file option when building an image
Title: Message Title
Quentin Nerden updated an issue
Jenkins / JENKINS-29085
Allow to use the docker build --file option when building an image
Change By:
Quentin Nerden
Allowtousethedockerbuild{{--file}}optionwhenbuildinganimageWewouldliketo not NOT havetheDockerfileattherootoftheproject,andhaveeverythingdockerrelatedinasubfolderdocker.Thenwewouldbuildtheimagewith{{dockerbuild-tmyrepo/myproject:v01--filedocker/Dockerfile.}}'.'isthedockercontext,meaningeventhoughtheDockerfileisinasubfolder'docker',dockercanstillaccesseverythingunder'.'(therootoftheproject).Itisnotpossibleotherwisetoaccessfoldersoutsideofthecontext,inaDockerfile(using{{ADD../scr/myfile.jar/srv/lib/}},forexample.'..'isnotallowed).Soitwouldbenicetostillhavetheoption:-DirectoryDockerfileisin(equivalentof--filepath)-Dockercontext.Note:Inthecode,thisseemstobeinfunctionbuildAndTag()infile:{{src/main/java/com/cloudbees/dockerpublish/DockerBuilder.java}}{{Stringcontext=defined(getDockerfilePath())? getDockerfilePath():.; lastResult=executeCmd(dockerbuild-t+i.next() +((isNoCache())?--no-cache=true:)+ +((isForcePull())?--pull=true:)+ +context);}}Theline{{Stringcontext=defined(getDockerfilePath())}}shouldbechangedsothatDockerfilePathisnotthesameascontext.Thoseshouldbedifferentthings.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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
[JIRA] [docker-build-publish-plugin] (JENKINS-29085) Allow to use the docker build --file option when building an image
Title: Message Title Quentin Nerden created an issue Jenkins / JENKINS-29085 Allow to use the docker build --file option when building an image Issue Type: Bug Assignee: Carlos Sanchez Components: docker-build-publish-plugin Created: 25/Jun/15 4:05 PM Environment: Jenkins 1.6.10 CloudBees Docker Build and Publish plugin version 1.0 Ubuntu 14.04 Priority: Minor Reporter: Quentin Nerden Allow to use the docker build --file option when building an image We would like to not have the Dockerfile at the root of the project, and have everything docker related in a subfolder docker. Then we would build the image with docker build -t myrepo/myproject:v01 --file docker/Dockerfile . '.' is the docker context, meaning even though the Dockerfile is in a subfolder 'docker', docker can still access everything under '.' (the root of the project). It is not possible otherwise to access folders outside of the context, in a Dockerfile (using ADD../scr/myfile.jar /srv/lib/ ,for example. '..' is not allowed). So it would be nice to still have the option: Directory Dockerfile is in (equivalent of --file path)
[JIRA] [docker-build-publish-plugin] (JENKINS-29085) Allow to use the docker build --file option when building an image
Title: Message Title
Quentin Nerden updated an issue
Jenkins / JENKINS-29085
Allow to use the docker build --file option when building an image
Change By:
Quentin Nerden
Allowtousethedockerbuild {{ --file }} optionwhenbuildinganimageWewouldliketonothavetheDockerfileattherootoftheproject,andhaveeverythingdockerrelatedinasubfolderdocker.Thenwewouldbuildtheimagewith{{dockerbuild-tmyrepo/myproject:v01--filedocker/Dockerfile.}}'.'isthedockercontext,meaningeventhoughtheDockerfileisinasubfolder'docker',dockercanstillaccesseverythingunder'.'(therootoftheproject).Itisnotpossibleotherwisetoaccessfoldersoutsideofthecontext,inaDockerfile(using{{ADD../scr/myfile.jar/srv/lib/}},forexample.'..'isnotallowed).Soitwouldbenicetostillhavetheoption:-DirectoryDockerfileisin(equivalentof--filepath)-Dockercontext.Note:Inthecode,thisseemstobeinfunctionbuildAndTag()infile:{{src/main/java/com/cloudbees/dockerpublish/DockerBuilder.java}}{{Stringcontext=defined(getDockerfilePath())? getDockerfilePath():.; lastResult=executeCmd(dockerbuild-t+i.next() +((isNoCache())?--no-cache=true:)+ +((isForcePull())?--pull=true:)+ +context);}}Theline{{Stringcontext=defined(getDockerfilePath())}}shouldbechangedsothatDockerfilePathisnotthesameascontext.Thoseshouldbedifferentthings.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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
[JIRA] [docker-build-publish-plugin] (JENKINS-27229) Docker publish plugin throws error Please login prior to push after publishing the image
Title: Message Title Quentin Nerden edited a comment on JENKINS-27229 Re: Docker publish plugin throws error Please login prior to push after publishing the image ***UPDATE***afterupgradingthepluginfrom0.15to1.0,theproblemisgone,itworksforme. ***UPDATE2***Docker1.6usestheV2registryofDockerhubbydefault.TheV2registryurlshouldnotbespecified. Ihavethesameproblem,withtheregistryhttps://registry-1.docker.io/v2(officialv2registryforDockerhub).Docker1.6.2isused,andthejenkins.dockercfgfilewasdeletedbeforerunningthejob.Theerrorinthejob'sconsoleis:(...)workspace]$dockerlogin-ujenkinsuser-ejenkins-u...@compcom-phttps://registry-1.docker.io/v2/WARNING:logincredentialssavedin/opt/jenkins/.dockercfg.LoginSucceeded[workspace]$dockerbuild-tmydocker/repo:873$WORKSPACE/targetSendingbuildcontexttoDockerdaemon557.1kB(...)SendingbuildcontexttoDockerdaemon98.04MBSendingbuildcontexttoDockerdaemon98.59MBSendingbuildcontexttoDockerdaemon98.59MBSendingbuildcontexttoDockerdaemonStep0:FROMmydocker/repo:base2---55604c2a11e7Step1:ADDcomp-web.war/server/standalone/deployments/---e1a25eef96e3Removingintermediatecontainer0118fd978788Successfullybuilte1a25eef96e3[workspace]$dockerpushmydocker/repo:873Thepushreferstoarepository[mydocker/repo](len:1)e1a25eef96e3:BufferingtoDiske1a25eef96e3:ImagepushfailedPleaseloginpriortopush:Username:EOFBuildstep'DockerBuildandPublish'markedbuildasfailure Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [docker-build-publish-plugin] (JENKINS-27229) Docker publish plugin throws error Please login prior to push after publishing the image
Title: Message Title Quentin Nerden edited a comment on JENKINS-27229 Re: Docker publish plugin throws error Please login prior to push after publishing the image UPDATE:afterupgradingthepluginfrom0.15to1.0,theproblemisgone,itworks! Ihavethesameproblem,withtheregistryhttps://registry-1.docker.io/v2(officialv2registryforDockerhub).Docker1.6.2isused,andthejenkins.dockercfgfilewasdeletedbeforerunningthejob.Theerrorinthejob'sconsoleis:(...)workspace]$dockerlogin-ujenkinsuser-ejenkins-u...@compcom-phttps://registry-1.docker.io/v2/WARNING:logincredentialssavedin/opt/jenkins/.dockercfg.LoginSucceeded[workspace]$dockerbuild-tmydocker/repo:873$WORKSPACE/targetSendingbuildcontexttoDockerdaemon557.1kB(...)SendingbuildcontexttoDockerdaemon98.04MBSendingbuildcontexttoDockerdaemon98.59MBSendingbuildcontexttoDockerdaemon98.59MBSendingbuildcontexttoDockerdaemonStep0:FROMmydocker/repo:base2---55604c2a11e7Step1:ADDcomp-web.war/server/standalone/deployments/---e1a25eef96e3Removingintermediatecontainer0118fd978788Successfullybuilte1a25eef96e3[workspace]$dockerpushmydocker/repo:873Thepushreferstoarepository[mydocker/repo](len:1)e1a25eef96e3:BufferingtoDiske1a25eef96e3:ImagepushfailedPleaseloginpriortopush:Username:EOFBuildstep'DockerBuildandPublish'markedbuildasfailure Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [docker-build-publish-plugin] (JENKINS-27229) Docker publish plugin throws error Please login prior to push after publishing the image
Title: Message Title Quentin Nerden edited a comment on JENKINS-27229 Re: Docker publish plugin throws error Please login prior to push after publishing the image ***UPDATE***afterupgradingthepluginfrom0.15to1.0,theproblemisgone,itworks ! forme. Ihavethesameproblem,withtheregistryhttps://registry-1.docker.io/v2(officialv2registryforDockerhub).Docker1.6.2isused,andthejenkins.dockercfgfilewasdeletedbeforerunningthejob.Theerrorinthejob'sconsoleis:(...)workspace]$dockerlogin-ujenkinsuser-ejenkins-u...@compcom-phttps://registry-1.docker.io/v2/WARNING:logincredentialssavedin/opt/jenkins/.dockercfg.LoginSucceeded[workspace]$dockerbuild-tmydocker/repo:873$WORKSPACE/targetSendingbuildcontexttoDockerdaemon557.1kB(...)SendingbuildcontexttoDockerdaemon98.04MBSendingbuildcontexttoDockerdaemon98.59MBSendingbuildcontexttoDockerdaemon98.59MBSendingbuildcontexttoDockerdaemonStep0:FROMmydocker/repo:base2---55604c2a11e7Step1:ADDcomp-web.war/server/standalone/deployments/---e1a25eef96e3Removingintermediatecontainer0118fd978788Successfullybuilte1a25eef96e3[workspace]$dockerpushmydocker/repo:873Thepushreferstoarepository[mydocker/repo](len:1)e1a25eef96e3:BufferingtoDiske1a25eef96e3:ImagepushfailedPleaseloginpriortopush:Username:EOFBuildstep'DockerBuildandPublish'markedbuildasfailure Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [docker-build-publish-plugin] (JENKINS-27229) Docker publish plugin throws error Please login prior to push after publishing the image
Title: Message Title Quentin Nerden edited a comment on JENKINS-27229 Re: Docker publish plugin throws error Please login prior to push after publishing the image *** UPDATE : *** afterupgradingthepluginfrom0.15to1.0,theproblemisgone,itworks!Ihavethesameproblem,withtheregistryhttps://registry-1.docker.io/v2(officialv2registryforDockerhub).Docker1.6.2isused,andthejenkins.dockercfgfilewasdeletedbeforerunningthejob.Theerrorinthejob'sconsoleis:(...)workspace]$dockerlogin-ujenkinsuser-ejenkins-u...@compcom-phttps://registry-1.docker.io/v2/WARNING:logincredentialssavedin/opt/jenkins/.dockercfg.LoginSucceeded[workspace]$dockerbuild-tmydocker/repo:873$WORKSPACE/targetSendingbuildcontexttoDockerdaemon557.1kB(...)SendingbuildcontexttoDockerdaemon98.04MBSendingbuildcontexttoDockerdaemon98.59MBSendingbuildcontexttoDockerdaemon98.59MBSendingbuildcontexttoDockerdaemonStep0:FROMmydocker/repo:base2---55604c2a11e7Step1:ADDcomp-web.war/server/standalone/deployments/---e1a25eef96e3Removingintermediatecontainer0118fd978788Successfullybuilte1a25eef96e3[workspace]$dockerpushmydocker/repo:873Thepushreferstoarepository[mydocker/repo](len:1)e1a25eef96e3:BufferingtoDiske1a25eef96e3:ImagepushfailedPleaseloginpriortopush:Username:EOFBuildstep'DockerBuildandPublish'markedbuildasfailure Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [docker-build-publish-plugin] (JENKINS-27229) Docker publish plugin throws error Please login prior to push after publishing the image
Title: Message Title Quentin Nerden commented on JENKINS-27229 Re: Docker publish plugin throws error Please login prior to push after publishing the image I have the same problem, with the registry https://registry-1.docker.io/v2 (official v2 registry for Dockerhub). Docker 1.6.2 is used, and the jenkins .dockercfg file was deleted before running the job. The error in the job's console is: (...) workspace] $ docker login -u jenkinsuser -e jenkins-u...@compcom -p https://registry-1.docker.io/v2/ WARNING: login credentials saved in /opt/jenkins/.dockercfg. Login Succeeded [workspace] $ docker build -t mydocker/repo:873 $WORKSPACE/target Sending build context to Docker daemon 557.1 kB (...) Sending build context to Docker daemon 98.04 MB Sending build context to Docker daemon 98.59 MB Sending build context to Docker daemon 98.59 MB Sending build context to Docker daemon Step 0 : FROM mydocker/repo:base2 --- 55604c2a11e7 Step 1 : ADD comp-web.war /server/standalone/deployments/ --- e1a25eef96e3 Removing intermediate container 0118fd978788 Successfully built e1a25eef96e3 [workspace] $ docker push mydocker/repo:873 The push refers to a repository [mydocker/repo] (len: 1) e1a25eef96e3: Buffering to Disk e1a25eef96e3: Image push failed Please login prior to push: Username: EOF Build step 'Docker Build and Publish' marked build as failure Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [docker-build-publish-plugin] (JENKINS-27229) Docker publish plugin throws error Please login prior to push after publishing the image
Title: Message Title Quentin Nerden reopened an issue Jenkins / JENKINS-27229 Docker publish plugin throws error Please login prior to push after publishing the image Change By: Quentin Nerden Resolution: CannotReproduce Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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.
