-
Notifications
You must be signed in to change notification settings - Fork 153
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
Adding the swagger configuration/openapispec to the repository #719
Comments
I generally have nothing against it. Not so sure what would be the benefit in having a swagger doc in this plugin. Can you explain what you intend to do? |
This is what the Jenkins community is trying to achieve : Developers need to know what to expect in terms of responses for each REST API endpoint, so external tools like jenkins-rest can be developed with confidence, and possibly with the help of some REST specification automation. For example, this could be done using the OpenAPI Specification (formerly known as Swagger Specification). Users of the REST API most often want: I thought of trying to start with the relatively simple ( in terms of number of endpoints one can access ) plugin and add a swagger-configuration to demonstrate how it might be done, Hence i thought this plugin would be the best to start with. |
Ok, sure go ahead. Let me know if you Need assist |
What feature do you want to see added?
As per the proposed project to "Standardizing Jenkins REST API documentation using Swagger or the OpenAPI specifications" by the jenkins team. I would like your suggestion on whether it would be okay to work on the openapispec/swagger configuration for this project as a demonstration on how it might be done and what changes would be possible.
Upstream changes
No response
Are you interested in contributing this feature?
I have already started working on creating the swagger configuration and am facing some significant issues and would like some help.
Thank you.
The text was updated successfully, but these errors were encountered: