Hi Oleg, The jenkins-cloud-plugin is bound to the internals of OpenShift engine and allows the engine to provision slave nodes when a user enables Jenkins functionality for his application. The slaves are used exclusively by the Jenkins cartridge that runs on OpenShift and is not usable outside that environment. This plugin is not intended as a general purpose plugin to be used by external Jenkins instances and is rather tied to the specific use-case of how OpenShift engine uses Jenkins[1].
The openshift-plugin I have created is focused on exposing the OpenShift client tools[2] functionality in Jenkins jobs which can be used in any Jenkins instance to orchestrate deployments on OpenShift. Considering different goals the two plugins pursue, I believe it makes sense to keep them separate. Kind Regards, Siamak [1] https://developers.openshift.com/en/managing-continuous-integration.html [2] https://developers.openshift.com/en/getting-started-client-tools.html On Sunday, October 26, 2014 8:25:02 AM UTC+1, Oleg Nenashev wrote: > > Hi Siamak, > > Please explain the difference from > https://github.com/openshift/jenkins-cloud-plugin > Is there any possibility to merge your functionality to the referenced > plugin? > > Best regards, > Oleg Nenashev > > суббота, 25 октября 2014 г., 13:31:18 UTC+4 пользователь Siamak > Sadeghianfar написал: >> >> Hi, >> >> I have developed a plugin for integrating Jenkins jobs to OpenShift PaaS. >> This includes creating containers on OpenShift and deploying applications >> to it. Could you create a repo and give me commit access? >> >> Plugin Name: OpenShift Plugin >> GitHub Account: siamaksade >> GitHub Repo: https://github.com/siamaksade/openshift-jenkins-plugin >> >> Thank you, >> Siamak >> >> -- 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]. For more options, visit https://groups.google.com/d/optout.
