You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When sending a POST to this url <JENKINS_HOST>/manage/configuration-as-code/check with a valid JCasC file the endpoint returns status code 200 and a empty list.
when doing the exact same call but with an invalid JCasC file we get status code 500, and a HTML page with a generic stapler response saying A problem occurred while processing the request, I would expected this to return status code 200 ( 400 Bad Request / 409 Conflict or similar ) a list containing all the errors in the invalid file.
What feature do you want to see added?
When sending a POST to this url <JENKINS_HOST>/manage/configuration-as-code/check with a valid JCasC file the endpoint returns status code 200 and a empty list.
when doing the exact same call but with an invalid JCasC file we get status code 500, and a HTML page with a generic stapler response saying
A problem occurred while processing the request
, I would expected this to return status code 200 ( 400 Bad Request / 409 Conflict or similar ) a list containing all the errors in the invalid file.The curl command we use for succesful testing
The Failing command
Upstream changes
No response
The text was updated successfully, but these errors were encountered: