Hey folks,
Glad to see all the attention on this topic. Let’s do more testing! :-)
CI that we have internally
--
At schuberg philis we have a “cloudstack integration test” (CIT) environment.
It’s grown and evolved incrementally over time along with our use of
cloudstack,
> -Original Message-
> From: Pierre-Luc Dion [mailto:pd...@cloudops.com]
> Sent: Thursday, August 21, 2014 11:21 AM
> To: dev@cloudstack.apache.org
> Cc: Will Stevens
> Subject: Re: [DISCUSSION] CI
>
> On Thu, Aug 21, 2014 at 1:32 PM, Edison Su wrote:
>
On Thu, Aug 21, 2014 at 1:32 PM, Edison Su wrote:
>
>
> > -Original Message-
> > From: Pierre-Luc Dion [mailto:pd...@cloudops.com]
> > Sent: Thursday, August 21, 2014 5:06 AM
> > To: dev@cloudstack.apache.org
> > Cc: Will Stevens
> > Subject:
> -Original Message-
> From: Pierre-Luc Dion [mailto:pd...@cloudops.com]
> Sent: Thursday, August 21, 2014 5:06 AM
> To: dev@cloudstack.apache.org
> Cc: Will Stevens
> Subject: Re: [DISCUSSION] CI
>
> Thanks for you responses,
>
> The revamp of marvin look
Thanks for you responses,
The revamp of marvin look promising, I'll have a closer look at it, even if
I'm not Python fan ;). In our side, we have close to fully automated
installation of CloudStack, XenServer hypervisor and an initial zone
creation. Our missing part is automated test cases to us
I use rspec in Ruby these days and find it get complex to maintain
pretty quickly. It's good for dealing with REST apis and middleware
but with Marvin (and python in general) I find infrastructure handling
easier. Stack traces of BDD code is also a little bit hard to
troubleshoot and comprehend. I
> -Original Message-
> From: Pierre-Luc Dion [mailto:pd...@cloudops.com]
> Sent: Wednesday, August 20, 2014 11:20 AM
> To: dev@cloudstack.apache.org; Will Stevens
> Subject: [DISCUSSION] CI
>
> I'd like to move this discussion out of the GIT workflow thread.
>
> Do we have any CI strate
