Closed adityasood closed 5 years ago
/cc @chrislovsund
There was a similar problem with environment variables being not set vs "".
I think the right place to fix it is the ConfigConverter
in gocd server because it will deal with all plugins returning null value. See how I fixed https://github.com/gocd/gocd/pull/4696
@tomzo yes you are right this is to be done at the server side. closing this issue.
Issue Type
Summary
Getting "500 Internal Server Error" when calling pipelines API for pipelines backed by config repo with YAML config. Seems to be because of missing
destination
K/V in YAML and JSON.Environment
Basic environment details
18.10.0 (7703-42d1cbe661161b5400289ead86c0447c84af8c0a)
1.8.0_171
Linux 3.10.0-693.2.2.el7.x86_64
curl and node
Additional Environment Details
Steps to Reproduce
destination
key, will get HTTP 500 error.destination
to ci.gocd.yaml file.destination: ""
key works fine.See config in code snippet below. curl: (22) The requested URL returned error: 500 Server Error
Adding
destination: ""
makes it work fine.Expected Results
Actual Results
Possible Fix
Work around is to add:
destination: ""
keyLog snippets
Code snippets/Screenshots
Any other info