Did you well selected amazon credentials in build and publish build step configuration ?
2016-04-11 22:53 GMT+02:00 A. Best <[email protected]>: > *Versions used in testing:* > Jenkins: 1.642.3 > Amazon ECR Plugin: 1.0 > <https://wiki.jenkins-ci.org/display/JENKINS/Amazon+ECR> > Cloudbees Docker Build & Publish: 1.2.1 > <https://wiki.jenkins-ci.org/display/JENKINS/CloudBees+Docker+Build+and+Publish+plugin> > > *ECS Container Instance* > Docker Version: 1.9.1 > API Version: 1.21 > > > I have a couple of quick question about the amazon-ecr-plugin > <https://wiki.jenkins-ci.org/display/JENKINS/Amazon+ECR>. > > In the About > <https://wiki.jenkins-ci.org/display/JENKINS/Amazon+ECR#AmazonECR-About> > section > of the plugin, the Cloudbees Docker Build and Publish > <https://wiki.jenkins-ci.org/display/JENKINS/CloudBees+Docker+Build+and+Publish+plugin> > is > referenced as an example of how the ECR plugin can be used. > > For my specific use case, I have the Jenkins master connecting to a > Jenkins JNLP slave running in an ECS cluster. I’m using a container based > on the jenkinsci/jnlp-slave > <https://hub.docker.com/r/jenkinsci/jnlp-slave/> to perform the build. > With the right permissions and mounted volumes, I am able to use the docker > host(which is the ECS container instance) to build docker images. > > > <https://lh3.googleusercontent.com/-KDL4GXfm5w0/VwwHwOiZQfI/AAAAAAAAAAY/jkj3Uzrhcm0NYeVpLyaRrmDF69oFxtL8Q/s1600/Screen%2BShot%2B2016-04-11%2Bat%2B4.20.38%2BPM.png> > > > The *Docker Build and Publish* plugin does use the dockerfile at the root > of the project and build it as expected. However, I’m running into an issue > when the plugin attempts to push the image to ECR. > > The push refers to a repository > [<my-user-id>.dkr.ecr.us-east-1.amazonaws.com/ > <http://amazonaws.com/flask-signup>test-repository] (len: 1)7a8e1872c5e2: > Preparing > Post > https://<my-user-id>.dkr.ecr.us-east-1.amazonaws.com/v2/test-repository/blobs/uploads/ > <http://amazonaws.com/v2/flask-signup/blobs/uploads/>: no basic auth > credentials > Build step 'Docker Build and Publish' marked build as failure > Finished: FAILURE > > It seems that the build is attempting to push to the registry with no > credentials. I was assuming that the ECR plugin would provide docker with > the correct AWS credentials to login to the registry so that the newly > built image could be pushed. > > Do I need any additional packages installed on the Jenkins slave to get > this to work? > > Am I missing something? > > Are my expectations for the plugin wrong? > > > Thanks, > > Adam > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/eaf6f71a-9758-4838-bb05-fd4fa43ee021%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-users/eaf6f71a-9758-4838-bb05-fd4fa43ee021%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANMVJzkbcHPGFmQD%3DWknEaKQf3%2BpM7KLmnk9FPVs0Qy_pNzPSA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
