[JIRA] (JENKINS-49771) token is never set so is constantly refreshed.
Title: Message Title Max Laverse stopped work on JENKINS-49771 Change By: Max Laverse Status: In Progress Open 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-49771) token is never set so is constantly refreshed.
Title: Message Title Max Laverse resolved as Fixed Jenkins / JENKINS-49771 token is never set so is constantly refreshed. Change By: Max Laverse Status: Open Resolved Resolution: Fixed 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-49771) token is never set so is constantly refreshed.
Title: Message Title Max Laverse started work on JENKINS-49771 Change By: Max Laverse Status: Open In Progress 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-49771) token is never set so is constantly refreshed.
Title: Message Title Max Laverse commented on JENKINS-49771 Re: token is never set so is constantly refreshed. I believe this is fixed in version 0.3.1. Please let me know if that's not the case. 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-49771) token is never set so is constantly refreshed.
Title: Message Title Max Laverse commented on JENKINS-49771 Re: token is never set so is constantly refreshed. A pull-request including some refactoring is out: https://github.com/jenkinsci/kubernetes-credentials-plugin/pull/3 I'll see if I can get someone to review it and then merge Thanks for reporting 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-49771) token is never set so is constantly refreshed.
Title: Message Title James Nord created an issue Jenkins / JENKINS-49771 token is never set so is constantly refreshed. Issue Type: Bug Assignee: Max Laverse Components: kubernetes-credentials-plugin Created: 2018-02-27 14:16 Priority: Minor Reporter: James Nord Nothing is ever stored in the OpenShiftBearerTokenCredentialImpl.token so the refresh call is constantly refreshing the token. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
