[JIRA] (JENKINS-49385) containers exit early in docker-workflow 1.15
Title: Message Title Wojciech Duda commented on JENKINS-49385 Re: containers exit early in docker-workflow 1.15 Christoph Forster I just saw that the bugfix was done as part of JENKINS-41278 and is released, version number is 1.15.1. Trying the update now. 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-49385) containers exit early in docker-workflow 1.15
Title: Message Title Wojciech Duda commented on JENKINS-49385 Re: containers exit early in docker-workflow 1.15 I encountered the same issue and had to revert Docker Workflow Plugin. A fix would be highly appreciated. 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-42152) Docker Pipeline causes build to fails because of use of --force=yes for tagging
Title: Message Title Wojciech Duda commented on JENKINS-42152 Re: Docker Pipeline causes build to fails because of use of --force=yes for tagging I did a small update to the PR but that was done blind, had no time to test it. WIll be able to do that tomorrow evening CEST, if somebody wants to try in the meantime please let me know about your results. 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-41148) Jenkins Pipeline still uses --force=yes for Docker Pipeline plugin
Title: Message Title Wojciech Duda commented on JENKINS-41148 Re: Jenkins Pipeline still uses --force=yes for Docker Pipeline plugin Jo Vandeginste Jack Brooks Pull request for https://issues.jenkins-ci.org/browse/JENKINS-42152 will be updated today. 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-42152) Docker Pipeline causes build to fails because of use of --force=yes for tagging
Title: Message Title Wojciech Duda commented on JENKINS-42152 Re: Docker Pipeline causes build to fails because of use of --force=yes for tagging Will update the PR today, seems it is not working for everyone. 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-42152) Docker Pipeline causes build to fails because of use of --force=yes for tagging
Title: Message Title Wojciech Duda commented on JENKINS-42152 Re: Docker Pipeline causes build to fails because of use of --force=yes for tagging Added pull request at https://github.com/jenkinsci/docker-workflow-plugin/pull/90 , code reviews welcome. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41148) Jenkins Pipeline still uses --force=yes for Docker Pipeline plugin
Title: Message Title Wojciech Duda commented on JENKINS-41148 Re: Jenkins Pipeline still uses --force=yes for Docker Pipeline plugin I actually created a pull request for JENKINS-42152 already, hopefully my code is solid enough to be accepted. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41148) Jenkins Pipeline still uses --force=yes for Docker Pipeline plugin
Title: Message Title Wojciech Duda edited a comment on JENKINS-41148 Re: Jenkins Pipeline still uses --force=yes for Docker Pipeline plugin [~jhovell] There is actually abug and this should not have been closed. If you for example try to push an image, tag it and then push the second tag (i.e. you want to push "latest" and a version, the build will fail on the tagging part with docker 1.12 and higher. I created https://issues.jenkins-ci.org/browse/JENKINS-42152 as a report for this.[~sa_jbrooks] was right, the code has not been fixed. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-41148) Jenkins Pipeline still uses --force=yes for Docker Pipeline plugin
Title: Message Title Wojciech Duda commented on JENKINS-41148 Re: Jenkins Pipeline still uses --force=yes for Docker Pipeline plugin John Hovell There is actually abug and this should not have been closed. If you for example try to push an image, tag it and then push the second tag (i.e. you want to push "latest" and a version, the build will fail on the tagging part with docker 1.12 and higher. I created https://issues.jenkins-ci.org/browse/JENKINS-42152 as a report for this. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-42152) Docker Pipeline causes build to fails because of use of --force=yes for tagging
Title: Message Title Wojciech Duda commented on JENKINS-42152 Re: Docker Pipeline causes build to fails because of use of --force=yes for tagging Looking at https://issues.jenkins-ci.org/browse/JENKINS-41148?focusedCommentId=284247=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-284247, the fix introduced in v1.4 of the plugin was temporary and does not work if you try to execute on Docker 1.12 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-42152) Docker Pipeline causes build to fails because of use of --force=yes for tagging
Title: Message Title
Wojciech Duda edited a comment on JENKINS-42152
Re: Docker Pipeline causes build to fails because of use of --force=yes for tagging
I also tried writing the last stage as: {code} stage('publish image') {myImage.push("${tagVersion}")myImage.push('latest') } {code} with exactly the same result.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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-42152) Docker Pipeline causes build to fails because of use of --force=yes for tagging
Title: Message Title
Wojciech Duda commented on JENKINS-42152
Re: Docker Pipeline causes build to fails because of use of --force=yes for tagging
I also tried writing the last stage as: stage('publish image') { myImage.push("$ {tagVersion} ") myImage.push('latest') } with exactly the same result.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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-42152) Docker Pipeline causes build to fails because of use of --force=yes for tagging
Title: Message Title
Wojciech Duda created an issue
Jenkins / JENKINS-42152
Docker Pipeline causes build to fails because of use of --force=yes for tagging
Issue Type:
Bug
Assignee:
Unassigned
Components:
docker-workflow-plugin
Created:
2017/Feb/17 4:33 PM
Environment:
Jenkins 2.32.2 Docker 1.12.3 Docker Pipeline Plugin 1.10
Priority:
Major
Reporter:
Wojciech Duda
First off, I verify that I have read other tickets relating to similar issues, especially https://issues.jenkins-ci.org/browse/JENKINS-41140. I am convinced this is not a duplicate. This Jenkinsfile exits and fails the build as soon as I try to do a Image.push('tag') with error code 125.
#!groovy
// define name of project
projectBaseName = 'gradle'
node {
def tagVersion= sh(script:"git tag -l --sort=-creatordate | head -n 1", returnStdout: true)
echo tagVersion
stage('checkout') {
checkout scm: [
$class: 'GitSCM',
userRemoteConfigs: [[credentialsId: 'erentodevsSSH', url: 'g...@github.com:erento/infra-gradle.git']],
branches: [[name: "refs/tags/${tagVersion}"]]],
changelog: false,
poll: false
}
def myImage
stage('build image') {
myImage = docker.build("eu.gcr.io/erento-docker/${projectBaseName}")
}
stage('publish image') {
myImage.push "${tagVersion}"
myImage.push 'latest'
}
}
Here is the end of the log where the build fails:
