pulse00 / digitalocean-plugin Goto Github PK

Hello,
I tried to debug the issue with slaves and found that the provisioning is not supported
Feb 28, 2018 8:12:00 AM hudson.slaves.NodeProvisioner$2 run WARNING: Unexpected exception encountered while provisioning agent jenkins-JenkinsDOPlugin-dashboardng.artifact.slave-072f820a-ab3b-4eb9-8595-86a39d6235e9 java.lang.AssertionError at com.dubture.jenkins.digitalocean.SlaveTemplate.provision(SlaveTemplate.java:229) at com.dubture.jenkins.digitalocean.Cloud$1.call(Cloud.java:224) at com.dubture.jenkins.digitalocean.Cloud$1.call(Cloud.java:216) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:748)

1.I think support several image sizes will be good
2.When I am choosing the sizes I see no difference
3.Notify on such kind error in Jenkins UI - I think must

Whilst this plugin spins up instances fine, they don't appear to be cleaned up once the "idle time" is reached. I set it to some extremely low value, ie. one or two minutes, but the expensive (!) instance was still "on". The build node log did not contain any new lines once the idle time was reached.

Let me know if I can collect any other data.

It would be great if there was a way to destroy a node if it has handled a certain number of builds. For example, if a node has handled 99 builds, destroy it when the 100th build finishes so a new instance could be created. Sometimes cruft builds up on these nodes and it's helpful to destroy it every so often.

This exists in the EC2 plugin now but I don't know enough Java to make it work here in the digitalocean plugin. 😢

https://wiki.jenkins-ci.org/display/JENKINS/DigitalOcean+Plugin

The latest version available there is 0.12...