Thanks, Kohsuke, I take over the slave-setup-plugin.
As it seems that a slave setup process with different requirements is developing in different new plugins (customtools-plugin, copy-to-slave-plugin, etc...) I would like to consolidate these approaches as it seems, that every idea has it's own background and may get into conflict if two different slave setup plugins need to be used. I don't know, if the slave-setup-plugin will be the final all-in-one-plugin or another or new one. At the end, I would suggest to execute a "GC" on that, if possible. @community to all "kind of slave-setup-plugin" developers: I would appreciate if you just let me know, which plugin you develop and how it is used (not in use, still developing, in production use, ...). I collect these information and will try to recognize the requirements for the all-in-one-slave-setup-plugin. Thank you all! Regards, Frederik 2012/2/14 Kohsuke Kawaguchi <[email protected]> > > Thanks, and sorry for the delay. I've merged the changes, and also added > you as a committer so that you can make changes without me becoming the > bottleneck. > > I'm releasing the new version given that JENKINS-11053 is a pretty severe > problem. > > Also, I don't think I have enough cycles to actively maintain this, so if > you'd be willing to take it over and take it forward, please feel free to > do so. > > > > On 02/09/2012 08:27 AM, ffromm wrote: > >> I made some changes to the slave-setup-plugin: >> >> - fixed missing templates >> - added checkbox to redeploy slave setup files and execute command >> line on system configuration save. >> >> Please take al ook at https://github.com/jenkinsci/** >> slave-setup-plugin/pull/1<https://github.com/jenkinsci/slave-setup-plugin/pull/1> >> >> Thanks! Frederik >> >> > > -- > Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/ > Try Nectar, our professional version of Jenkins >
