Hi, The best practice is to try to add your customizations to the original plugin. If your customizations change existing behavior, add corresponding options. See also: https://wiki.jenkins-ci.org/display/JENKINS/Before+starting+a+new+plugin#Beforestartinganewplugin-maintainer
Regards, Fred On Monday, August 31, 2015 at 11:15:49 PM UTC+2, Jacqueline Taing wrote: > > Hi, > > I am making customizations to the existing Simple Parameterized Build > Report plugin > <https://github.com/nullin/simple-parameterized-builds-report> to fit our > needs: limit number of builds to show to a configurable MAX_DAYS property, > change the text of URL in report to include build time and build duration, > change URL of builds in report to point to aggregated test results (which > uses another plugin). > > > I have forked the repository in my local workspace but I was wondering > what are the general best practices when making extensions to existing > plugins: > > 1. Do you rename the repository to something else (e.g. > simple-parameterized-build-report to something else) > 2. Do you change the plugin name to something else? > 3. What version should be used? > > Thanks, > -jacqui > -- 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/00a122e0-fd99-489c-b03b-0efeeb66d137%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
