Request for hosting : vmware-vrealize-automation-plugin
55 views
Skip to first unread message
Inky Sea
Dec 14, 2015, 2:13:58 PM12/14/15
to Jenkins Developers
GitHub repository URL : https://github.com/inkysea/vmware-vrealize-automation-plugin
GitHub user : inkysea
jenkins-ci.org user : inkysea
Description: The VMware vRealize Automation plugin allows Jenkins to provision virtual machines and application blueprints on vRrealize Automation v7+.
Inky Sea
Dec 17, 2015, 10:15:45 AM12/17/15
to Jenkins Developers
What is the typical turn around on creating the project? It's a busy time of year, I just want to ensure that this request did not get lost in the shuffle.
Baptiste Mathus
Dec 17, 2015, 11:07:20 AM12/17/15
to jenkin...@googlegroups.com
I don't know enough about it, but just to check: is this a product really different from VMWare/VSphere (both exist)?
Shouldn't/Couldn't it be integrated in one existing plugin as an extension or something?
(Not saying it should, again, just for the record trying to get your take/opinion about it before eventually forking)
Thanks!
--
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 jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/d5f4bb89-0352-4f4f-98b8-5bd52787f276%40googlegroups.com.
Inky Sea
Dec 17, 2015, 12:46:47 PM12/17/15
to Jenkins Developers, m...@batmat.net
VMware's vRealize Automation (vRA) is a cloud management platform that allows provisioning on various type of infrastructure. For example, vRA can provision workloads to vSphere, HyperV, AWS, Azure, etc...
The other VMware/VSphere plugins are for different products in the VMware suite. Attempting to integrate with those plugins would be a challenge from a development perspective as each product does different things and it would be confusing to the end users.
Christopher Orr
Dec 17, 2015, 2:58:05 PM12/17/15
to jenkin...@googlegroups.com
Fair enough.
If you could remove the "-plugin" suffix from your artifact ID, that
would be great (it's listed in the prerequisites here:
https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Prerequisites)
Thanks,
Chris
On 17/12/15 18:46, Inky Sea wrote:
> VMware's vRealize Automation (vRA) is a cloud management platform that
> allows provisioning on various type of infrastructure. For example,
> vRA can provision workloads to vSphere, HyperV, AWS, Azure, etc...
>
> The other VMware/VSphere plugins are for different products in the
> VMware suite. Attempting to integrate with those plugins would be a
> challenge from a development perspective as each product does different
> things and it would be confusing to the end users.
>
> On Thursday, December 17, 2015 at 11:07:20 AM UTC-5, Baptiste Mathus wrote:
>
> I don't know enough about it, but just to check: is this a product
> really different from VMWare/VSphere (both exist)?
> Shouldn't/Couldn't it be integrated in one existing plugin as an
> extension or something?
>
> (Not saying it should, again, just for the record trying to get your
> take/opinion about it before eventually forking)
>
> Thanks!
>
> 2015-12-17 16:15 GMT+01:00 Inky Sea <inkyse...@gmail.com <javascript:>>:
>
> GitHub user : inkysea
> jenkins-ci.org <http://jenkins-ci.org> user : inkysea
If you could remove the "-plugin" suffix from your artifact ID, that
would be great (it's listed in the prerequisites here:
https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Prerequisites)
Thanks,
Chris
On 17/12/15 18:46, Inky Sea wrote:
> VMware's vRealize Automation (vRA) is a cloud management platform that
> allows provisioning on various type of infrastructure. For example,
> vRA can provision workloads to vSphere, HyperV, AWS, Azure, etc...
>
> The other VMware/VSphere plugins are for different products in the
> VMware suite. Attempting to integrate with those plugins would be a
> challenge from a development perspective as each product does different
> things and it would be confusing to the end users.
>
> On Thursday, December 17, 2015 at 11:07:20 AM UTC-5, Baptiste Mathus wrote:
>
> I don't know enough about it, but just to check: is this a product
> really different from VMWare/VSphere (both exist)?
> Shouldn't/Couldn't it be integrated in one existing plugin as an
> extension or something?
>
> (Not saying it should, again, just for the record trying to get your
> take/opinion about it before eventually forking)
>
> Thanks!
>
>
> What is the typical turn around on creating the project? It's a
> busy time of year, I just want to ensure that this request did
> not get lost in the shuffle.
>
> On Monday, December 14, 2015 at 2:13:58 PM UTC-5, Inky Sea wrote:
>
> GitHub repository URL :
> https://github.com/inkysea/vmware-vrealize-automation-plugin <https://github.com/inkysea/vmware-vrealize-automation-plugin>
> What is the typical turn around on creating the project? It's a
> busy time of year, I just want to ensure that this request did
> not get lost in the shuffle.
>
> On Monday, December 14, 2015 at 2:13:58 PM UTC-5, Inky Sea wrote:
>
> GitHub repository URL :
>
> GitHub user : inkysea
> jenkins-ci.org <http://jenkins-ci.org> user : inkysea
Inky Sea
Dec 17, 2015, 3:13:18 PM12/17/15
to Jenkins Developers
Oleg Nenashev
Dec 19, 2015, 3:57:17 AM12/19/15
to Jenkins Developers
+1 from me for vmware-vrealize-automation
Seems it's ready to go
четверг, 17 декабря 2015 г., 23:13:18 UTC+3 пользователь Inky Sea написал:
Seems it's ready to go
четверг, 17 декабря 2015 г., 23:13:18 UTC+3 пользователь Inky Sea написал:
Daniel Beck
Dec 22, 2015, 5:58:24 PM12/22/15
to jenkin...@googlegroups.com
Forked to https://github.com/jenkinsci/vmware-vrealize-automation-plugin
Also created a component on issues.jenkins-ci.org and made you default assignee.
Welcome aboard!
Also created a component on issues.jenkins-ci.org and made you default assignee.
Welcome aboard!
> --
> 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 jenkinsci-de...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/46b65d13-9165-4dce-acfb-f5b388e8d3c1%40googlegroups.com.
> 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 jenkinsci-de...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages