cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Prasanna Santhanam <>
Subject Re: [PROPOSAL] Using continuous integration to maintain our code quality...
Date Thu, 15 May 2014 04:11:05 GMT
On Wed, May 14, 2014 at 06:21:34PM +0000, Alex Huang wrote:
> I think infrastructure code should just be checked in with the
> source code.  To separate it means you have to deal with version
> match/mismatch between infrastructure and source code.  

Sorry - that doesn't sound right. Usually infrastructure code has
little to do with the source code other than deploying the packages
built from said source. Could you please clarify the bits that go into
this infra code and why it should be affected by versions? [*] If it's
config management recipes those are usually maintained separate from
source of your web-tier. Infra code is maintained and changed usually
more rapidly. I don't get why jenkins settings and config management
should exist within our catch-all tools dir. We're going to bloat it
up unnecessarily and realise later it should have been a separate repo
to begin with - for eg. cloudmonkey or marvin.

[*] the wiki did not have enough information about the infra-code


Powered by

View raw message