[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 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-50833) NoSuchMethodError causing Pipeline editor to not see agent settings
Title: Message Title Alex White commented on JENKINS-50833 Re: NoSuchMethodError causing Pipeline editor to not see agent settings I noticed this issue yesterday after using Pipeline and Blue Ocean for the first time and was very confused. I tried downgrading to Pipeline 2.4 from 2.5 but it still appears that `pipeline-model-definition 1.2.8` is the dependency there. I don't see a way to easily downgrade that specific dependency 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.
