cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From imduffy15 <>
Subject [GitHub] cloudstack-cloudmonkey pull request: Build a CI environment in ord...
Date Sat, 10 Jan 2015 09:51:47 GMT
GitHub user imduffy15 opened a pull request:

    Build a CI environment in order to allow automated testing

    Hi All,
    I'm creating this pull request to get some assistance with finishing an idea.
    I thought it would be neat if we could bring up Apache Cloudstack on TravisCI under simulator
mode and execute some cloudmonkey scripts to do the configuration and verify the responses.

    The pull request at the moment causes TravisCI to bring up an environment with:
     - Mysql installed with password "password".
     - Cloudstack 4.3.2 running on port 8080 with the simulator sql stuff imported into the
db. At the moment I have it blocking on this, in the future this would be a background task.
    Any assistance with the following is welcome:
     - cloudmonkey scripts to configure cloudstack in simulator mode. (Just like marvin does)
     - the output generated by cloudmonkey should be verified in some way. Perhaps just simple
greping for now?
     - we can finish at this point or introduce some other scripts to generate more cloudmonkey
outputs that we can verify. 
    Thoughts? Ideas? Shoot downs?

You can merge this pull request into a Git repository by running:

    $ git pull master

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2
commit 76e0723c480aae10f5a955c87af3dc9577ec5e01
Author: Ian Duffy <>
Date:   2015-01-10T09:43:51Z

    Bring up Cloudstack simulator in a travis environment


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message