dave-hagedorn / jenkins-runner

VS Code plugin to develop and run Jenkins Pipeline scripts
MIT License
30 stars 8 forks source link

Error: jenkins: job.config: jenkins: crumbIssuer.get: not found #10

Closed mrumeshkumar closed 5 years ago

mrumeshkumar commented 5 years ago

Hi Team, I am getting this exception while trying to run my Jenkin file from VsCode.


[2019-06-17 17:09:51.301] [Jenkins] [info] Creating Jenkins instance @url=http://inblresdpjkp02.eng.med.ge.com, with user=xxxxxx, password=**** [2019-06-17 17:09:51.302] [Jenkins] [info] Creating pipeline build using job test-pipeline @http://inblresdpjkp02.eng.med.ge.com, with params undefined [2019-06-17 17:09:51.302] [Jenkins] [info] Fetching remote XML config for job test-pipeline @http://inblresdpjkp02.eng.med.ge.com [2019-06-17 17:10:01.756] [Jenkins] [info] Parsing and updating XML with new pipeline script [2019-06-17 17:10:01.774] [Jenkins] [info] Pushing remote XML config for job test-pipeline @http://inblresdpjkp02.eng.med.ge.com [2019-06-17 17:10:09.129] [Jenkins] [error] Error starting job test-pipeline #undefined @http://inblresdpjkp02.eng.med.ge.com}: Error: jenkins: job.config: jenkins: crumbIssuer.get: not found [2019-06-17 17:10:09.129] [Jenkins] [error]

Error 404 Not Found

HTTP ERROR 404

Problem accessing /crumbIssuer/api/json. Reason:

    Not Found


Powered by Jetty://

[2019-06-17 17:10:13.457] [Jenkins] [info] Stopping job test-pipeline #undefined @http://inblresdpjkp02.eng.med.ge.com [2019-06-17 17:10:13.457] [Jenkins] [info] Stopping job test-pipeline #undefined @http://inblresdpjkp02.eng.med.ge.com

cvakiitho commented 5 years ago

I fixed this by enabling CSRF protection with default crumb https://support.cloudbees.com/hc/en-us/articles/219257077-CSRF-Protection-Explained

dave-hagedorn commented 5 years ago

I forgot to update the docs in the 1.2.0 release, but you can also use the useCrumbIssuer field on a host defined in settings.

CSRF protection will not be used if this is set to false.

dave-hagedorn commented 5 years ago

Closing - I think this issue is resolved, but please re-open if you experience any more problems.