[JIRA] [amazon-ecr-plugin] (JENKINS-34958) Getting "Your Authorization Token has expired" when using ECR credentials
Title: Message Title Luis Silva edited a comment on JENKINS-34958 Re: Getting "Your Authorization Token has expired" when using ECR credentials Faced this same issue today with this plugin today .Configuring ECR in us-east-1 region ( ***.dkr.ecr.us-east-1.amazonaws.com/*** ) the push succeeds.But using ECR in eu-west-1 ( ***.dkr.ecr.eu-west-1.amazonaws.com/*** ) it fails: with an error:error parsing HTTP 403 response body: unexpected end of JSON input: ""Build step 'Docker Build and Publish' marked build as failureIt's the exact same job and settings, only changing the registry endpoint in the job.Using the command line to issue a push with the token obtained by the jenkins job (set in ~/.docker/config.json) also fails, but using the aws cli to get the token, issuing a docker login and then push works fine regardless of the region.That leads to me to believe the problem is somewhere in the token / credentials issue code as you mentioned.Any ETA on the fix for this problem?Docker version 1.11.1, build 5604cbe/1.11.1Amazon ECR plugin: 1.3CloudBees Docker Build and Publish plugin: 1.2.2Docker Commons Plugin: 1.3.1 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] [amazon-ecr-plugin] (JENKINS-34958) Getting "Your Authorization Token has expired" when using ECR credentials
Title: Message Title Luis Silva commented on JENKINS-34958 Re: Getting "Your Authorization Token has expired" when using ECR credentials Faced this same issue today with this plugin today. Configuring ECR in us-east-1 region ( **.dkr.ecr.us-east-1.amazonaws.com/** ) the push succeeds. But using ECR in eu-west-1 ( **.dkr.ecr.eu-west-1.amazonaws.com/** ) it fails: with an error: error parsing HTTP 403 response body: unexpected end of JSON input: "" Build step 'Docker Build and Publish' marked build as failure It's the exact same job and settings, only changing the registry endpoint in the job. Using the command line to issue a push with the token obtained by the jenkins job (set in ~/.docker/config.json) also fails, but using the aws cli to get the token, issuing a docker login and then push works fine regardless of the region. That leads to me to believe the problem is somewhere in the token / credentials issue code as you mentioned. Any ETA on the fix for this problem? Docker version 1.11.1, build 5604cbe/1.11.1 Amazon ECR plugin: 1.3 CloudBees Docker Build and Publish plugin: 1.2.2 Docker Commons Plugin: 1.3.1 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] [amazon-ecr-plugin] (JENKINS-34958) Getting "Your Authorization Token has expired" when using ECR credentials
Title: Message Title Vesa Alho commented on JENKINS-34958 Re: Getting "Your Authorization Token has expired" when using ECR credentials I can confirm this issue. Works in us-east-1, but not eg. in eu-west-1. 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] [amazon-ecr-plugin] (JENKINS-34958) Getting "Your Authorization Token has expired" when using ECR credentials
Title: Message Title Kristoffer Peterhänsel edited a comment on JENKINS-34958 Re: Getting "Your Authorization Token has expired" when using ECR credentials So I can't quite manually provoke this error message using the AWS CLI tool and docker. But it does appear that the credentials issued are regional. So it seems this plugin may need a way to set the desired region. But so far I haven't found the place in the AmazonECRClient where you can actually specify region... Edit: And then of course I did find see it. 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] [amazon-ecr-plugin] (JENKINS-34958) Getting "Your Authorization Token has expired" when using ECR credentials
Title: Message Title Kristoffer Peterhänsel commented on JENKINS-34958 Re: Getting "Your Authorization Token has expired" when using ECR credentials So I can't quite manually provoke this error message using the AWS CLI tool and docker. But it does appear that the credentials issued are regional. So it seems this plugin may need a way to set the desired region. But so far I haven't found the place in the AmazonECRClient where you can actually specify region... 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] [amazon-ecr-plugin] (JENKINS-34958) Getting "Your Authorization Token has expired" when using ECR credentials
Title: Message Title Kristoffer Peterhänsel created an issue Jenkins / JENKINS-34958 Getting "Your Authorization Token has expired" when using ECR credentials Issue Type: Bug Assignee: Nicolas De Loof Components: amazon-ecr-plugin Created: 2016/May/19 2:14 PM Environment: Jenkins 2.4 Docker Build and Publish plugin 1.2.2 (+ PR #41) Priority: Blocker Reporter: Kristoffer Peterhänsel In an attempt to start moving away from our self-hosted Docker Registry. I came across this plugin to make it easier to push to Amazon ECR. And after a (fairly) quick fix of the Docker Build and Publish plugin. Time had come to make that happen. But instead I am getting the this error when it attempt to push. So something is wrong. The push refers to a repository [somerepo.dkr.ecr.eu-west-1.amazonaws.com/imagename] 1b29323a75d2: Preparing 5bf87793f977: Preparing 5ccb950f635d: Preparing 965c3fc60463: Preparing f354df03c5c3: Preparing 5f70bf18a086: Preparing 5f70bf18a086: Preparing 9523ecdf69b1: Preparing 5f70bf18a086: Preparing 5f70bf18a086: Preparing 5f70bf18a086: Preparing 5f70bf18a086: Preparing 6d7b4f405a28: Preparing 5f70bf18a086: Preparing 5f70bf18a086: Preparing 099efa904cb9: Preparing 8f83f19c7186:
