Custom Plugin Not Able to Authenticate with Registry

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Custom Plugin Not Able to Authenticate with Registry

Nathan Clark
Good Morning!

We are building a custom plugin based on Docker Build Publish that uses Source to Image to build the image on top of docker.

Everything works great except the last step: publish to registry (which in our case is ECR). 

We have the ECR Plugin installed, and it works for our traditional docker projects.

Our S2I projects, however, run `docker push...` and get the following:

denied: Your Authorization Token has expired. Please run 'aws ecr get-login' to fetch a new one.
Build step 'S2I Build and Publish' marked build as failure
Finished: FAILURE

Occasionally it will succeed, but we believe that this is due to unexpired credentials from one of the traditional docker projects.

We are looking at the differences between the original code:


And our own:


But have not been able to figure out what is missing.

Any guidance on using DockerRegistryEndpoint or DockerRegistryToken would be much appreciated!

Thanks in advance,

-N 

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/e2e5d808-e312-4066-a4cf-689a2d886b1b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.