I don't get the purpose of the plugin even after reading the code a bit. - Does it just iterate through steps file and checks patterns from another file? - How is it related to "API coverage"? It seems to be a generic checker of external JSON file - Where are the format descriptions/requirements? - If there's a support of specific tools, please mention them
FYI, sometimes its better to create pull requests and ask the community to review the code before the first release. - there are bad practices like storing non-transient Build classes in Reports. It may cause many issues n the cause of the improper usage. - FileNotFound exceptions should be converted to AbortException, because you know the failure reason - Strange JSON handling magic in the publisher code, could be significantly refactored and optimized - Inconsistent null/empty string checks in parameters from config.xml - etc. четверг, 13 августа 2015 г., 11:24:24 UTC+3 пользователь Priti Changlani написал: > > Hello there! > > This is a request to host a plugin called API Coverage. The details are: > > Url: https://github.com/rackerlabs/api-coverage > Repo name: api-coverage-plugin > Personal GitHub: pritic > Jenkins Account: pritichanglani > Description: The API Coverage plugin will serve as a tool to measure > testing of the API contract > > Thank you, > Priti > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/bbe3944f-df24-4f3d-aa11-6b5ffcdfda52%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
