-
Notifications
You must be signed in to change notification settings - Fork 711
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Discrepancy between schema and dynamic documentation in JCASC plugn #2241
Labels
Comments
Is anybody else experiencing similar issue? please let me know if you require more inputs to this thread |
The schema isn't accurate unfortunately, some stuff works but the work was never really finished |
Experiencing similar issues. Are there any efforts to finish the schema? How can I help? |
No efforts going on currently, any tested pull requests that improve the schema generation will be reviewed and merged. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Jenkins and plugins versions report
Environment
What Operating System are you using (both controller, and any agents involved in the problem)?
no applicable, using controller
Reproduction steps
agentProtocols:
Access schema https://{JENKINS_URL}/configuration-as-code/schema and search for same element: agentProtocols and result is as below:
"agentProtocols": {"type": "string"},
"local": {
"additionalProperties": false,
"type": "object",
Access jcasc documentation https://{JENKINS_URL}/configuration-as-code/reference and search for same element: agentProtocols and result is as below:
agentProtocols: list ofString
Expected Results
In jenkins. yaml file it is defined as array type and documentation is generating this type correctly as below.
The problem is with the schema output as same element is defined as string type and that is incorrect as it should be array.
Actual Results
It is a discrepancy for some type elements between dynamic documentation and schema which are provided by JCASC plugin.
Anything else?
No response
The text was updated successfully, but these errors were encountered: