We are currently in release close out mode. I hope to get some time to work on the cloud api after we get the release out... So hopefully something in the next couple of weeks.
As I said before, the hooks I need are in Jenkins 1.592+ so this new API can be added in a plugin targeting 1.592+ though obviously the threading issues with deprovisioning will only be resolved on 1.607+ ;-) On Sunday, May 31, 2015, Kanstantsin Shautsou <[email protected]> wrote: > Hi, Stephen. > I reviewed code in almost all cloud plugins and it seems to me that > jenkins cloud api (DockerSlave -> DockerComputer (Launcher/retention)) > looks not suitable for cloud usage at all. Some plugins just creating vm > and then passes hardcodes to this implemented classes, other do run in > Launcher.launch() that may end in issues. > > Do you have any draft versions or real plans for cloud-api plugin? > > On Saturday, April 25, 2015 at 1:33:45 AM UTC+3, Kanstantsin Shautsou > wrote: >> >> >> On Apr 25, 2015, at 01:13, Stephen Connolly < >> [email protected] >> <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote: >> >> >> >> On Friday, April 24, 2015, Kanstantsin Shautsou < >> [email protected] >> <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote: >> >>> I think all Cloud plugin developers will be glad to know about Cloud API >>> problems and their changes. >>> >> >> So my plan is to do a new cloud-api in a plugin. It makes it easier to >> update and experiment. I have sufficient changes made in core to allow for >> a new cloud api in a plugin that targets 1.588+ >> >> Sounds like a plan. >> >> >> >>> Really difficult to follow massive changes in core. Any comments about >>> docker-plugin will be appreciated. Also it will be very cool if you review >>> https://github.com/jenkinsci/jenkins/pull/1448 >>> >>> That pull request is just putting more lipstick in the pig. I see the >> use case you are after and I believe the correct approach is via a new >> cloud API that handles all the crazy that does need to be handled and >> removes the crazy that doesn't actually need to be there (but is needed for >> the current API) >> >> HTH (though probably not what you wanted to hear ;-) ) >> >> Well, feel free to provide cloud-api-plugin for mass review. Will be glad >> to help. >> > -- > 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] > <javascript:_e(%7B%7D,'cvml','jenkinsci-dev%[email protected]');> > . > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/f238d6f3-a48d-4336-a149-5b0aefee19af%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/f238d6f3-a48d-4336-a149-5b0aefee19af%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Sent from my phone -- 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/CA%2BnPnMwAnuO71PbOqvc3FJ7QaHDkN7fhCw%3DQ1TrscZXAVtsczw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
