I updated the pom.xml to reflect the changes. As for the name, Ratcheting is what it does. I suppose coverage-ratcheting-plugin might be more descriptive. The analysis should happen by a code coverage program; this plugin just passes or fails a build by comparing the current code coverage result to the historical code coverage threshold.
- Nathan Wiering From: Oleg Nenashev [mailto:[email protected]] Sent: Saturday, September 27, 2014 11:26 AM To: [email protected] Cc: Wiering, Nathan Subject: Re: New Jenkins plugin hosting request; Ratchet-plugin In my opinion, the plugin's name is too vague. Ratchet and Ratcheting words are just the slang without a valuable info about the real functionality (build log analysis?). Could you consider the plugin's renaming? Several proposals regarding pom.xml * groupId: What about com.mattersight.jenkinsci.plugins? * it's preferable to avoid uppercase letters in artifactId пятница, 26 сентября 2014 г., 23:02:47 UTC+4 пользователь Wiering, Nathan написал: Dear Jenkins dev team, I have been developing a ratcheting plugin for Jenkins for my company (Mattersight Corp.) that we would like to have hosted on the Jenkins Github. The goal of this plugin is to provide a means to ratchet on code coverage results- causing a build to fail if it drops below a threshold. GitHub plugin name: Ratchet-plugin Github id: "ntw1103" Github project to be forked: https://github.com/ntw1103/Ratchet Please let me know if there is anything else required. Thanks, Nathan Wiering -- 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]. For more options, visit https://groups.google.com/d/optout.
