> > > On Friday, April 24, 2015, Kanstantsin Shautsou <[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+ > > >> 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 ;-) ) > > Actually, *any* indication of forward movement is good to hear.
That patch is over 6 months old without any attention (which makes me sad, since passing data containers through a build pipeline would be extremely useful), and I'm sure there's been statements along the lines of "cloud API = bad = unusable" for perhaps twice as long as that. I'll happily spend time to adapt docker-plugin to a newer API. -- 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/CAPYP83T8GbFCwL5x7gEw9en8CAnY21BS8jPKf8qmcRAn_bLd5w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
