Request hosting for single-use-slave plugin

[Clayton O'Neill]

I've written a plugin that allows taking a slave offline each time it completes a job.  This is useful when used with tools like nodepool (http://ci.openstack.org/nodepool.html) which create single use slaves, but Jenkins will sometimes schedule another job on the slave before it can be removed.

Github plugin name: singleuseslave

Github ID: dvorak

Github repository: https://github.com/dvorak/singleuseslave-plugin

[Jesse Glick]

On Sat, Apr 18, 2015 at 8:52 AM, Clayton O'Neill
<clayton...@gmail.com> wrote:
> I've written a plugin that allows taking a slave offline each time it
> completes a job.

Like https://github.com/jenkinsci/durable-task-plugin/blob/a98cd9124145d494a153de130459c88b2acd208a/src/main/java/org/jenkinsci/plugins/durabletask/executors/OnceRetentionStrategy.java
I suppose?

[Clayton O'Neill]

It sounds similar, but it's directly useable by end users by specifying node labels that should be taken offline after they finish a job.  The JClouds  and Gearman plugins also have similar functionality, but it's not possible to use them without using everything else they bring.

[Clayton O'Neill]

Anything else I should do to get this considered for hosting? 

[Clayton O'Neill]

On Saturday, April 18, 2015 at 8:52:36 AM UTC-4, Clayton O'Neill wrote:

Would it be possible to get hosting for this plugin? 

[Baptiste Mathus]

In my mind, if as you say this plugin offers somehow the same feature, but for the end user, you should depend on that library plugin and reuse that class, and your plugin would concentrate on the UI part. Didn't you consider doing so?

IMO that would indirectly benefit the Jenkins users with more stability/reproducibility.

--
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/5a974927-18d6-49e3-ab99-b3ef87b11e80%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !

[Clayton O'Neill]

On Sun, May 3, 2015 at 9:41 AM, Baptiste Mathus wrote:

In my mind, if as you say this plugin offers somehow the same feature, but for the end user, you should depend on that library plugin and reuse that class, and your plugin would concentrate on the UI part. Didn't you consider doing so?

No, I didn't considering using the library, because I wasn't aware it existed or that it had some overlapping functionality.  As near as I can tell, the only way I could have known that would have been to happen upon it and happen to look in that particular source file.  I did a lot of research on this functionality before deciding to write this myself, and I'd have been glad not to have done as much work as I did.

 

IMO that would indirectly benefit the Jenkins users with more stability/reproducibility.

Having the plugin at all would directly benefit them.

I'd like to see this hosted, but I don't have the time or inclination to completely rewrite the plugin solely to make it prettier.  I'd also be concerned because https://issues.jenkins-ci.org/browse/JENKINS-27476 is still open and would appear to directly effect us.  We've been running our plugin for several months now with hundreds of builds per day without issue.