Yes, it is and what you said sounds good to me. Thanks, Phong.
On Monday, June 9, 2014 10:47:43 AM UTC-7, Ullrich Hafner wrote: > > Is CI not meant to be continuous integration? I think all Jenkins plugins > are related to CI? Typically, plug-in names should be as short as possible. > > Am 09.06.2014 um 16:19 schrieb Phong Nguyen Le <[email protected] > <javascript:>>: > > Thanks Ulli for quick response. The plugin name is slightly different from > the requested one. Don't you mind to rename it to elasticbox-ci-plugin? > > Best, > Phong. > > On Monday, June 9, 2014 7:00:32 AM UTC-7, Ullrich Hafner wrote: >> >> Created https://github.com/jenkinsci/elasticbox-plugin >> >> Welcome aboard! >> >> Ulli >> >> Am 09.06.2014 um 15:27 schrieb Phong Nguyen Le <[email protected]>: >> >> Dear Jenkins developers, >> >> I'd like to publish a new Jenkins plugin that provide full integration >> between Jenkins and ElasticBox (http://elasticbox.com). With this >> plugin, Jenkins can launch, provision, and manage Jenkins slaves on-demand >> in different cloud providers via ElasticBox. >> >> Plugin name: elasticbox-ci-plugin >> GitHub username: tphongio >> >> Thanks in advance, >> Phong. >> >> >> -- >> 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. >> >> >> > -- 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.
