We support passing in a valid OpenShift token as a bearer token with curl requests against a deployment of the OpenShift Jenkins image.
You should be able to leverage the curl based accessed noted at the link you posted. See https://github.com/openshift/jenkins-openshift-login-plugin#non-browser-access https://github.com/openshift/jenkins#jenkins-admin-user https://docs.openshift.org/latest/using_images/other_images/jenkins.html#jenkins-openshift-oauth-authentication On Thu, Jul 5, 2018 at 7:51 AM, Andrew Feller <afel...@bandwidth.com> wrote: > I imagine developers leveraging Jenkins declarative linter > <https://jenkins.io/doc/book/pipeline/development/#linter> from Jenkins > hosted within OpenShift is more difficult because OpenShift is handling > identity management, but has anyone had luck with supporting this? I > realize the nature of Jenkins makes this complicated so don't expect there > to be a great solution here. > > Thanks! > > -- > > [image: BandwidthMaroon.png] > > Andy Feller • Sr DevOps Engineer > > 900 Main Campus Drive, Suite 500, Raleigh, NC 27606 > > > e: afel...@bandwidth.com > > _______________________________________________ > users mailing list > users@lists.openshift.redhat.com > http://lists.openshift.redhat.com/openshiftmm/listinfo/users > >
_______________________________________________ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
