Those both plugins mentioned above (JenkinsLint as well as Disable Failed Job Plugin) do something different that our plugin is doing.
In our own system we detected over 240 out of over 1,500 jobs. These will get deleted soon by our plugin. Deactivation of the jobs aren't an option to us, because we want to have these jobs removed completely. The Disable Failed Job Plugin doesn't do this. As nice as JenkinsLint looks like: This is something completely different. The idea behind plugins is, that you can extend your instance with the features you want. I don't want to have the ultimate plugin, which does all the work. If this would be the case, nobody would need plugins. It could all be inside the core. But this isn't the case. Jochen -- View this message in context: http://jenkins-ci.361315.n4.nabble.com/Request-hosting-a-plugin-tp4761476p4761558.html Sent from the Jenkins dev mailing list archive at Nabble.com. -- 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/1437572720004-4761558.post%40n4.nabble.com. For more options, visit https://groups.google.com/d/optout.
