specific to a branch/tag.
Will - if we can include this in RC2, we can use the new packages for CI based
testing.
Thanks.
Regards.
From: Rohit Yadav
Sent: 20 July 2016 09:24:17
To: dev@cloudstack.apache.org
Subject: Re: [VOTE] Split Marvin to its own repository
systems to install marvin and run tests.
Regards.
From: williamstev...@gmail.com on behalf of Will
Stevens
Sent: 19 July 2016 22:52:35
To: dev@cloudstack.apache.org
Subject: Re: [VOTE] Split Marvin to its own repository
I think your alternatives makes sense.
Si
_
> From: williamstev...@gmail.com on behalf of
> Will Stevens
> Sent: 19 July 2016 22:32:26
> To: dev@cloudstack.apache.org
> Subject: Re: [VOTE] Split Marvin to its own repository
>
> So how would the different versions of Marvin be tracked and how would the
> ve
] Split Marvin to its own repository
So how would the different versions of Marvin be tracked and how would the
versions be associated with the supported ACS versions?
Because the ACS API changes, a Marvin version will only support a specific
set of ACS versions. We need to understand how that will
tegration with CI systems. Please share your thoughts on above ^^.
> Thanks.
>
>
> Regards.
>
> ____________
> From: Syed Ahmed
> Sent: 19 July 2016 21:41:44
> To: dev@cloudstack.apache.org
> Subject: Re: [VOTE] Split Marvin to its own repository
>
> I
Regards.
From: Syed Ahmed
Sent: 19 July 2016 21:41:44
To: dev@cloudstack.apache.org
Subject: Re: [VOTE] Split Marvin to its own repository
I believe it will make CI much smoother. Right now marvin is tied to the
Cloudstack repo which was fine if all the integration tests were running
from
to achieve by moving marvin into a separate repo.?
> >
> >
> > --Bharat.
> >
> >
> > From: Raja Pullela
> > Sent: Tuesday, July 19, 2016 5:30:20 PM
> > To: dev@cloudstack.apache.org
> > Subject: Re: [VOTE] Split Marvin to its own r
.
From: Rene Moser
Sent: 18 July 2016 17:32:57
To: dev@cloudstack.apache.org
Subject: Re: [VOTE] Split Marvin to its own repository
Hi
I used to use marvin for setup simulator environments for using it as
integration test environments (4.5-latest) for the Ansible CloudStack
modules.
It's
Subject: RE: [VOTE] Split Marvin to its own repository
Would it make sense to have tests include cloudstack versions along with
'other' requirements in their meta-data, so that they don't *have* to be tied
to a branch.
Kind regards,
Paul Angus
paul.an...@shapeblue.com
www.sha
eparate repo.?
>
>
> --Bharat.
>
>
> From: Raja Pullela
> Sent: Tuesday, July 19, 2016 5:30:20 PM
> To: dev@cloudstack.apache.org
> Subject: Re: [VOTE] Split Marvin to its own repository
>
> Hi Rohit,
>
> same question as Rene has poste
rom: Raja Pullela
>> Sent: Tuesday, July 19, 2016 5:30:20 PM
>> To: dev@cloudstack.apache.org
>> Subject: Re: [VOTE] Split Marvin to its own repository
>>
>> Hi Rohit,
>>
>> same question as Rene has posted, impact on older releases – will have
>> issues
Hi Rohit,
what are we trying to achieve by moving marvin into a separate repo.?
--Bharat.
From: Raja Pullela
Sent: Tuesday, July 19, 2016 5:30:20 PM
To: dev@cloudstack.apache.org
Subject: Re: [VOTE] Split Marvin to its own repository
Hi Rohit,
same question
Hi Rohit,
same question as Rene has posted, impact on older releases – will have issues
on older releases. I know that the older releases have marvin code which can
be used. Also, this will require changes on the CI side to pull the correct
repo for Marvin.
+1, if Bharat can modify CI imp
Hi
I used to use marvin for setup simulator environments for using it as
integration test environments (4.5-latest) for the Ansible CloudStack
modules.
It's been a while and I can not really remember exactly what it was
caused it to fail but since a few weeks I was not able to setup such an
envir
Would it make sense to have tests include cloudstack versions along with
'other' requirements in their meta-data, so that they don't *have* to be tied
to a branch.
Kind regards,
Paul Angus
paul.an...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeb
15 matches
Mail list logo
