Can't get api token from com.openshift.jenkins.plugnis.OpenShiftTokenCredentials in pipeline about jenkins-client-plugin HOT 5 CLOSED

OpenShiftTokenCredentials was ment to use for the Openshift plugin, If you need to use regular the token out of it why you don't use it as Secret Text?

from jenkins-client-plugin.

Understand it. The point is that our huge pipeline partially uses jenkins-client-plugin for openshift deployment and partially - it uses ansible playbooks for the same task (k8s plugin). It would be really great to have the same credential for both approaches. Historically, it was custom OpenShiftTokenCredentials.

from jenkins-client-plugin.

@maxt the relevant option for your case as suggested is to use a k8s Secret which will be synced as a Credential in Jenkins as well. Then, you can both use it in your Jenkins pipeline and with your ansible script.

wdyt?

from jenkins-client-plugin.

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

from jenkins-client-plugin.

/close

@maxt the relevant option for your case as suggested is to use a k8s Secret which will be synced as a Credential in Jenkins as well. Then, you can both use it in your Jenkins pipeline and with your ansible script.

wdyt?
I agree. I managed to negotiate for new bunch of credentials of type "Secret text" and it perfectly works for me.

from jenkins-client-plugin.