Request hosting a plugin

[Jochen A. Fuerbacher]

Hi there,

I'd like to host a plugin on jenkinc-ci.org.

URL to my Plugin:
https://github.com/Jochen-A-Fuerbacher/FailedJobDeactivator
Name of the repository: failedjobdeactivator-plugin
GitHub-ID: Jochen-A-Fuerbacher
jenkins-ci.org user name: JochenAFuerbacher
Description: The plugin detects jobs that haven't been built yet,
haven't been built successfully yet or haven't been built successfully
for a longer time. The administrator gets a quick overview of these
detected jobs and can decide to deactivate or delete these detected jobs
automatically (configurable using the Build Failure Analyzer Plugin),
update the job description page and notify users by e mail.

Thank you!
Jochen A. Fürbacher

[Christopher Orr]

I have the feeling this is something that could perhaps be integrated
with other similar plugins, e.g. the recently added JenkinsLint plugin?

Just a thought..
-Chris

[Jochen-A-Fuerbacher]

The FailedJobDeactivator plugin was developed as part of a bachelor thesis.
It not just detects wrong configured jobs, it also detects well configured
jobs, which are orphaned.
Example: A job gets nightly built. After a while, the project is old and
gets deleted from SCM (SVN, Git, ...). But the Job remains on the Jenkins.
So building the job fails and nobody takes care of it.

But thank you very much for giving me the info about the JenkinsLint plugin.
This looks pretty nice.

Jochen



--
View this message in context: http://jenkins-ci.361315.n4.nabble.com/Request-hosting-a-plugin-tp4761476p4761496.html
Sent from the Jenkins dev mailing list archive at Nabble.com.

[domi]

+1 for an integration/merge

> --
> 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 jenkinsci-de...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/1437553157289-4761496.post%40n4.nabble.com.
> For more options, visit https://groups.google.com/d/optout.

[Richard Bywater]

If not the Lint plugin already mentioned, then https://wiki.jenkins-ci.org/display/JENKINS/Disable+Failed+Job+Plugin would seem a bit of an overlap which might be good to merge with?

Richard

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/C7DE41F1-57B9-443F-8ECC-8DAD439F9117%40fortysix.ch.

[Jochen-A-Fuerbacher]

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

[Åsmund Østvold]

I like the destination of the plugin but....
As the number of jobs grow the number of plugins grow.  Many plugins are not maintained for a long period. Keeping similar features in one plugin reduce the risk of this happening. This increase the ease of use and administration of a Jenkins installation.

IMHO +1 for integration

--
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 jenkinsci-de...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/1437572720004-4761558.post%40n4.nabble.com.

[Jochen-A-Fuerbacher]

Does ist really reduce the risk of bad maintained plugins? I don't think so.
When merging plugins then the risk is higher that none of the features will
get maintained any longer. But when the features are implemented in own
plugins, then maybe some of the plugins aren't maintained, but some others
are.


Åsmund Østvold wrote

> I like the destination of the plugin but....
> As the number of jobs grow the number of plugins grow. Many plugins are
> not maintained for a long period. Keeping similar features in one plugin
> reduce the risk of this happening. This increase the ease of use and
> administration of a Jenkins installation.
>
> IMHO +1 for integration

--
View this message in context: http://jenkins-ci.361315.n4.nabble.com/Request-hosting-a-plugin-tp4761476p4761925.html

[domi]

IMO, History has shown that maintenance will more likely not been maintained.
…sure, everyone wants his own plugin, but its not the best for the community and the endusers too
my 2 cents...

> --
> 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 jenkinsci-de...@googlegroups.com.

> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/1437717839669-4761925.post%40n4.nabble.com.

[Daniel Beck]

Jochen is a colleague of Stefan Brausch at 1&1 and they maintain a dozen plugins or so, including Job Config History. I doubt this plugin being abandoning is going to be a problem.

This also seems to ask the wrong question -- what we need is better tools for dealing with 1000+ plugins, because no matter how hard we try, that number isn't going to go down. And that would make the issue of 'similar' plugins much less of an issue.

So, what problems have been mentioned?

- Too many plugins. We need better UI and tools to deal with that many plugins rather than not admitting new ones.
- Similar plugins. Nothing really wrong with that. They shouldn't be identical, but Build Timeout and Logfilesizechecker both abort builds. No reason that both shouldn't exist.
- Abandoned plugins. I think we're fairly safe from that POV as I mentioned above. That said, this plugin is a 'one trick pony' with little maintenance to begin with, and if it ever breaks, what really is lost? It doesn't look like it has that much to contribute to the Old Data Monitor, it wouldn't break your builds, … Let's face it, different plugins require different maintenance effort, and this is a low maintenance one.

While I can imagine this plugin getting merged into another one, I don't think it's necessary if the author disagrees.

> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/57127380-9162-4188-BF93-87D7B3AF8830%40fortysix.ch.