{"action":"created","issue":{"url":"https://api.github.com/repos/fabric8io/docker-maven-plugin/issues/991","repository_url":"https://api.github.com/repos/fabric8io/docker-maven-plugin","labels_url":"https://api.github.com/repos/fabric8io/docker-maven-plugin/issues/991/labels{/name}","comments_url":"https://api.github.com/repos/fabric8io/docker-maven-plugin/issues/991/comments","events_url":"https://api.github.com/repos/fabric8io/docker-maven-plugin/issues/991/events","html_url":"https://github.com/fabric8io/docker-maven-plugin/issues/991","id":313070909,"number":991,"title":"Double push causing quay.io issues","user":{"login":"jbarnettwomply","id":13838924,"avatar_url":"https://avatars2.githubusercontent.com/u/13838924?v=4","gravatar_id":"","url":"https://api.github.com/users/jbarnettwomply","html_url":"https://github.com/jbarnettwomply","followers_url":"https://api.github.com/users/jbarnettwomply/followers","following_url":"https://api.github.com/users/jbarnettwomply/following{/other_user}","gists_url":"https://api.github.com/users/jbarnettwomply/gists{/gist_id}","starred_url":"https://api.github.com/users/jbarnettwomply/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jbarnettwomply/subscriptions","organizations_url":"https://api.github.com/users/jbarnettwomply/orgs","repos_url":"https://api.github.com/users/jbarnettwomply/repos","events_url":"https://api.github.com/users/jbarnettwomply/events{/privacy}","received_events_url":"https://api.github.com/users/jbarnettwomply/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-04-10T20:07:45Z","updated_at":"2018-04-13T16:59:33Z","closed_at":null,"author_association":"NONE","body":"### Description\r\nWe're having sporadic issues pushing docker images to quay.io from builds running in CircleCI 2.0.  The error we're getting is:\r\nhttps://support.coreos.com/hc/en-us/articles/115000295693-Quay-reports-stale-images-when-pushing\r\nand we can see that the docker push goal kind of appears to be pushing twice:\r\n```\r\n2018-04-10T18:05:53:200+0000 [INFO] DOCKER> The push refers to a repository [quay.io/org/repo]\r\n2018-04-10T18:06:06:233+0000 [INFO] DOCKER> develop: digest: sha256:SHA_FOR_IMAGE size: 15213\r\n2018-04-10T18:06:06:238+0000 [INFO] DOCKER> Pushed quay.io/org/repo:develop in 13 seconds \r\n2018-04-10T18:06:06:243+0000 [INFO] DOCKER> The push refers to a repository [quay.io/org/repo]\r\n2018-04-10T18:06:12:795+0000 [INFO] DOCKER> develop: digest: sha256:SHA_FOR_IMAGE size: 15213\r\n```\r\n\r\ncan also see in quay's UI the following events, happening in the same minute:\r\n* develop was moved to SHA256 SHA_FOR_IMAGE from V1ID DOCKER_V1_ID  11:06 AM\r\n* develop was moved to SHA256 PREVIOUS_SHA_FOR_IMAGE from SHA256 PREVIOUS_SHA_FOR_IMAGE   11:06 AM\r\n\r\n* d-m-p version : 0.17.1\r\n* Maven version (`mvn -v`) :  3.2.5\r\n\r\nour build config resembles:\r\n```\r\n                            <build>\r\n                                <from>base_image</from>\r\n                                <maintainer>contact@info.com</maintainer>\r\n                                <tags>\r\n                                    <tag>${git.branch}</tag>\r\n                                </tags>\r\n                                <ports>\r\n                                    <port>${service.port}</port>\r\n                                </ports>\r\n                                <workdir>/app</workdir>\r\n                                <entryPoint>java -jar /app/${project.build.finalName}-shaded.jar</entryPoint>\r\n                                <assembly>\r\n                                    <mode>dir</mode>\r\n                                    <basedir>/app</basedir>\r\n                                    <user>app:app:app</user>\r\n                                    <inline>\r\n                                        <files>\r\n                                            <file>\r\n                                                <source>${project.build.directory}/${project.build.finalName}-shaded.jar</source>\r\n                                                <outputDirectory>.</outputDirectory>\r\n                                            </file>\r\n                                            <file>\r\n                                                <source>${project.build.directory}/bcprov-jdk15on.jar</source>\r\n                                                <outputDirectory>.</outputDirectory>\r\n                                            </file>\r\n                                        </files>\r\n                                    </inline>\r\n                                </assembly>\r\n                            </build>\r\n```\r\nnot sure if this is related to #925 or a separate issue?"},"comment":{"url":"https://api.github.com/repos/fabric8io/docker-maven-plugin/issues/comments/381198572","html_url":"https://github.com/fabric8io/docker-maven-plugin/issues/991#issuecomment-381198572","issue_url":"https://api.github.com/repos/fabric8io/docker-maven-plugin/issues/991","id":381198572,"user":{"login":"jbarnettwomply","id":13838924,"avatar_url":"https://avatars2.githubusercontent.com/u/13838924?v=4","gravatar_id":"","url":"https://api.github.com/users/jbarnettwomply","html_url":"https://github.com/jbarnettwomply","followers_url":"https://api.github.com/users/jbarnettwomply/followers","following_url":"https://api.github.com/users/jbarnettwomply/following{/other_user}","gists_url":"https://api.github.com/users/jbarnettwomply/gists{/gist_id}","starred_url":"https://api.github.com/users/jbarnettwomply/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jbarnettwomply/subscriptions","organizations_url":"https://api.github.com/users/jbarnettwomply/orgs","repos_url":"https://api.github.com/users/jbarnettwomply/repos","events_url":"https://api.github.com/users/jbarnettwomply/events{/privacy}","received_events_url":"https://api.github.com/users/jbarnettwomply/received_events","type":"User","site_admin":false},"created_at":"2018-04-13T16:59:33Z","updated_at":"2018-04-13T16:59:33Z","author_association":"NONE","body":"Updating to 0.25.1 and using the docker.skip.tag property appears to get rid of the double-push, so thinking this use case may be the inspiration for #925 / #926 --  it does seem weird to me that it pushes `repo:develop` twice though, should it be smart enough to skip the tag it just pushed?"}}
{"actor":{"display_login":"jbarnettwomply"}}