cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sergey Levitskiy <>
Subject Re: [GitHub] cloudstack issue #1658: Added an additional JSON diff output to the ApiXmlDo...
Date Mon, 12 Sep 2016 19:29:32 GMT
@swill @jburwell From my, non-committer, point of view introducing fully automated test system
integrated with PR submission and leveraging complete list of supported hypervisors is the
key to stability. I really like blueorangutain idea and if this can be brought back and also
cover full set of integration tests along with packaging that would be awesome. When we develop
PR unfortunately we can only test it only with a certain set of hypervisors and network configs
so although giving test LGTM it doesn’t cover all possible integration points. I believe
most other test results people execute manually and post on PRs are the same.

On 9/12/16, 11:38 AM, "jburwell" <> wrote:
    Github user jburwell commented on the issue:
        @swill where hardware are being varies by PR.  In some cases, we have people running
them in their labs and reporting results.  Other cases, it's blueorangatan going through ShapeBlue
Jenkins + trillian.  But yes, PRs are getting tested on hardware.
        (Sadly, we are still recovering from a dead storage array, so blueorangatan has been
out of commission for a little bit),
    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