[JIRA] (JENKINS-50557) GCR Credentials Plugin does not work
Title: Message Title Alex White edited a comment on JENKINS-50557 Re: GCR Credentials Plugin does not work 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. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50557) GCR Credentials Plugin does not work
Title: Message Title Alex White edited a comment on JENKINS-50557 Re: GCR Credentials Plugin does not work 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. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50557) GCR Credentials Plugin does not work
Title: Message Title Alex White edited a comment on JENKINS-50557 Re: GCR Credentials Plugin does not work 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. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50557) GCR Credentials Plugin does not work
Title: Message Title Taylor Patton updated an issue Jenkins / JENKINS-50557 GCR Credentials Plugin does not work 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 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50557) GCR Credentials Plugin does not work
Title: Message Title Alex White commented on JENKINS-50557 Re: GCR Credentials Plugin does not work 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. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50557) GCR Credentials Plugin does not work
Title: Message Title Taylor Patton commented on 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 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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] (JENKINS-50557) GCR Credentials Plugin does not work
Title: Message Title Joseph Hughes created an issue Jenkins / JENKINS-50557 GCR Credentials Plugin does not work Issue Type: 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 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
