Your approach sounds very reasonable. The same approach is used by the xunit plugin (converts different test results to JUnit format) and a similar but slightly different approach is used by the warnings plugin (converts different warning logs to an object model). I think that both of these approaches make sense. With the former one you can reuse the UI completely from the target format. The disadvantage is that there might be some information loss when converting to another format (there is coverage data *and* source code if I remember correctly: everything must be supported by the target). With the latter approach you can define the model on your own. However, you need to write the UI again (or adapt one of the other ones). So I think the simpler solution would be your suggested approach. Here you need to carefully select which of the tools (and which Jenkins plugin) should be the target.
> Am 15.03.2018 um 08:41 schrieb Rajgure Abhishek Sanjay Abhishek Sanjay > <[email protected]>: > > > Various plugins are available which currently implement code > coverage (jacoco, > EclEmma,clover plugin, cobertura plugin, clover php plugin, etc), Instead of > having one plugin for each code coverage > > result it would be best if we could merge them all into one plugin which will > handle code coverage. > > > my approach > develope intermediate converters for each code coverage reporting tool which > will convert its result into one format > develope a jenkins plugin which is collection of this converters as well as > it has functionality of showing combined result > > In Past week i was able to convert jacoco results into cobertura result, > and converted jacoco files are recognized by cobertura plugin of jenkins so i > was able to see combined result of previous cobertura result in addition to > this converted result > > > -- > 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] > <mailto:[email protected]>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/cdf3a75a-3a0a-44b1-aa37-b24c64161350%40googlegroups.com > > <https://groups.google.com/d/msgid/jenkinsci-dev/cdf3a75a-3a0a-44b1-aa37-b24c64161350%40googlegroups.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- 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/EBC5B89B-1703-4FBB-B5B7-304C64F22731%40gmail.com. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: Message signed with OpenPGP
