[JIRA] (JENKINS-50557) GCR Credentials Plugin does not work

396 views
Skip to first unread message

JJHughes57@gmail.com (JIRA)

unread,
Apr 3, 2018, 11:35:02 PM4/3/18
to jenkinsc...@googlegroups.com
Joseph Hughes created an issue
 
Jenkins / Bug JENKINS-50557
GCR Credentials Plugin does not work
Issue Type: Bug Bug
Assignee: Wei Z
Components: google-container-registry-auth-plugin
Created: 2018-04-04 03:34
Environment: Jenkins ver. 2.109
Labels: docker
Priority: Blocker Blocker
Reporter: Joseph Hughes

All builds trying to use this plugin result in the following... 

ERROR: Could not find credentials matching gcr:SOMEPROJECT
hudson.AbortException: Could not find credentials matching gcr:plasma-column-128721
	at org.jenkinsci.plugins.docker.commons.credentials.DockerRegistryEndpoint.newKeyMaterialFactory(DockerRegistryEndpoint.java:217)
	at org.jenkinsci.plugins.docker.commons.credentials.DockerRegistryEndpoint.newKeyMaterialFactory(DockerRegistryEndpoint.java:204)
	at org.jenkinsci.plugins.docker.commons.credentials.DockerRegistryEndpoint.newKeyMaterialFactory(DockerRegistryEndpoint.java:196)
	at com.cloudbees.dockerpublish.DockerBuilder$Perform.executeCmd(DockerBuilder.java:455)
	at com.cloudbees.dockerpublish.DockerBuilder$Perform.executeCmd(DockerBuilder.java:431)
	at com.cloudbees.dockerpublish.DockerBuilder$Perform.buildAndTag(DockerBuilder.java:373)
	at com.cloudbees.dockerpublish.DockerBuilder$Perform.exec(DockerBuilder.java:311)
	at com.cloudbees.dockerpublish.DockerBuilder$Perform.access$100(DockerBuilder.java:291)
	at com.cloudbees.dockerpublish.DockerBuilder.perform(DockerBuilder.java:262)
	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744)
	at hudson.model.Build$BuildExecution.build(Build.java:206)
	at hudson.model.Build$BuildExecution.doRun(Build.java:163)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)
	at hudson.model.Run.execute(Run.java:1727)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
	at hudson.model.ResourceController.execute(ResourceController.java:97)
	at hudson.model.Executor.run(Executor.java:429)
Build step 'Docker Build and Publish' marked build as failure
Finished: FAILURE

I have tried different Domains and putting the credentials in many places but nothing works. 

It happens in pipeline jobs and also the Build and Publish Plugin. 

The plugin is broken and does not work. 
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

taylorp36@gmail.com (JIRA)

unread,
Apr 8, 2018, 7:16:02 PM4/8/18
to jenkinsc...@googlegroups.com
Taylor Patton commented on Bug JENKINS-50557
 
Re: GCR Credentials Plugin does not work

Are you sure you have both "Google OAuth Credentials plugin" and "Google Container Registry Auth Plugin" installed? Also make sure that your actual jenkins credential ID is not prepended with "gcr:". Those were my 2 mistakes

abobwhite89@gmail.com (JIRA)

unread,
May 14, 2018, 8:12:02 AM5/14/18
to jenkinsc...@googlegroups.com

I am seeing the same thing. This worked about a week ago but something changed and I've been searching for two days on what the issue is. Using the Google credentials via kubernetes metadata. Driving my crazy that this simple thing won't work.

taylorp36@gmail.com (JIRA)

unread,
May 16, 2018, 12:24:02 AM5/16/18
to jenkinsc...@googlegroups.com
Taylor Patton updated an issue
 
Change By: Taylor Patton
Comment:
Are you sure you have both "Google OAuth Credentials plugin" and "Google Container Registry Auth Plugin" installed? Also make sure that your actual jenkins credential ID is not prepended with "gcr:". Those were my 2 mistakes

abobwhite89@gmail.com (JIRA)

unread,
May 16, 2018, 11:10:02 AM5/16/18
to jenkinsc...@googlegroups.com
Alex White edited a comment on Bug JENKINS-50557
I am seeing the same thing. This worked about a week ago but something changed and I've been searching for two days on what the issue is. Using the Google credentials via kubernetes metadata. Driving my crazy that this simple thing won't work.


 

UPDATE: I ended up just using `

gcloud auth activate-service-account --key-file $FILE` and then `

gcloud auth configure-docker` followed by a regular docker push to avoid this issue.

abobwhite89@gmail.com (JIRA)

unread,
May 16, 2018, 11:10:03 AM5/16/18
to jenkinsc...@googlegroups.com

abobwhite89@gmail.com (JIRA)

unread,
May 16, 2018, 11:10:03 AM5/16/18
to jenkinsc...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages