On 21/08/15 12:44, Catalin Luta wrote: > We do realize that some people would require the functionality that JIRA > Test Result Publisher has, but there would be two options for that: > - use both plugins concurrently > - add the functionality of the Result Publisher plugin to our own
The second option could be possible — I believe there have been some plugins that have replaced (or are intended to replace) existing plugins, where the new plugin includes the existing plugin's features, and takes over the existing plugin's artifact ID, allowing existing users to upgrade. But in this case, it needs to be made sure that the new plugin migrates users' settings from the existing plugin correctly. > I, for one, would suggest adding the functionality to our > infrastructure, because that would take less time to achieve and we have > a more robust infrastructure. "Robust infrastructure" and a GitHub repository with zero tests in it don't really go together IMO ;) I'm sure adding the existing code to your plugin without replacing the existing plugin would "take less time" for *you*, but it would be terrible for everyone else, and that's why we want to prevent plugin proliferation. So (if you want to release the plugin via the Jenkins update centre), taking over the existing plugin and including its functionality might be the best solution. Regards, Chris -- 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/55D7AEF6.3060303%40orr.me.uk. For more options, visit https://groups.google.com/d/optout.
