I did something similar with a reverse proxy. The proxy embeds the token in
the request to openshift.
On Fri, Feb 8, 2019, 9:30 AM Gabe Montero You need to provide a bearer token with sufficient permissions to all the
> OpenShift project(s) involved.
>
> A quick example on how to get such a
You need to provide a bearer token with sufficient permissions to all the
OpenShift project(s) involved.
A quick example on how to get such a token is at
https://github.com/openshift/jenkins-openshift-login-plugin#non-browser-access
Apply what is done for the example curl invocation to the
Hi,
Using the generic webhook trigger plugin myself, while still relying on
OpenShift authentication logging into Jenkins, I don't remember having
anything like this.
Although I can't explain why your plugin would refuse this, unless maybe
something's wrong in Jenkins permissions matrix?
As far
Hi Graham,
We don't use any OpenShift build configs so unfortunately that won't
work for us.
The builds are orchestrated completely by Jenkins so the webhook has
to be posted to Jenkins itself, not OpenShift.
Thanks,
Sean
On Fri, 8 Feb 2019 at 17:14, Graham Dumpleton wrote:
>
> I believe
I believe you should be using the web book URL from the pipeline build config.
You can get them from the web console page for the pipeline.
See:
*
https://ruddra.com/posts/openshift-python-gunicorn-nginx-jenkins-pipelines-part-three/
Hi,
I have Jenkins running in an OpenShift cluster and I have a multi
branch job set up, with the source git repository residing in
Bitbucket server.
I wan't to set up a web hook from Bitbucket Server to Jenkins to
trigger builds as soon as there are changes to the repo. In a vanilla
Jenkins