If a test is meddling with the infrastructure then we have two options: 1. isolate the test and run it separately when other tests aren't running 2. prepare a deployment with those nfs storage preconfigured.
It can be difficult to always get the infra right for a test so tests often will skip themselves if they run in unsuitable infrastructure. So yes - its never going to be 100% automatable. On Wed, Sep 11, 2013 at 12:43:32AM -0600, Marcus Sorensen wrote: > But if the test requires some sort of preconfiguration, what then (e.g. > test NFS primary storage would need a local or remote NFS configured)? do I > need to roll my own, or can I touch the existing test infra and do the > preconfigure? > On Sep 11, 2013 12:34 AM, "Prasanna Santhanam" <t...@apache.org> wrote: > > > Yes - Once your test goes into the repo, it should get picked in the > > subsequent > > run. > > > > Jenkins installations from various companies can be combined into a single > > landing page. Jenkins itself doesn't support master/slave but it does > > through > > the gearman plugin. It's something I have tried using with VMs but not with > > real infra - but it is entirely possible. > > > > On Tue, Sep 10, 2013 at 11:17:53PM -0700, Ahmad Emneina wrote: > > > I think there are jenkins slaves that run the nicera plugins on/at > > Schuberg > > > Philis housed infrastructure. The Citrix jenkins nodes also runs as > > slaves > > > that connect back to the apache owned/controlled jenkins. No reason why > > > testing infra need be so consolidated, it just so happens no one is > > putting > > > their hardware where their mouth is. > > > > > > I also assume if your marvin tests get accepted upstream, they'll be > > > included in the nightly runs/reports. Prasanna correct me if I'm wrong. > > > > > > > > > On Tue, Sep 10, 2013 at 11:02 PM, Marcus Sorensen <shadow...@gmail.com > > >wrote: > > > > > > > CloudStack Dev, > > > > I was emailed about some of the testing questions I brought up > > > > over the last few threads, and a few things were pointed out to me > > > > that I think we should try to remedy. Primarily, that the testing > > > > environment is owned by Citrix, the QA team is primarily Citrix-run, > > > > and the testing done is focused on the use models that Citrix > > > > develops. > > > > I've been assured that the test infrastructure is for everyone, > > > > and I'm not at all trying to say that there's a problem with Citrix > > > > focusing their work on their own interests, but I'm not sure that > > > > anyone outside of Citrix really knows how to add their own stuff to > > > > this testing infrastructure (perhaps for lack of trying, I don't > > > > know). > > > > I haven't really put together enough thought to know how to tackle > > > > this, but my gut tells me that we need some sort of community-owned > > > > testing roll-up, where everyone can do their own testing in whatever > > > > infrastructure and submit hourly, daily, weekly results. If my test > > > > fits into the Citrix test infrastructure and I can figure out how to > > > > get it there, great. If not, I can roll my own and integrate it via > > > > some API. For example the SolidFire guys may wan to run automated > > > > regression testing. That probably won't be doable in the Citrix > > > > infrastructure, but they may want to script a daily > > > > git-pull/build/deploy zone/create volume and it seems logical that > > > > we'd want to support it. > > > > Thoughts? Anyone have experience with such things? Can we have a > > > > master/slave scenario with Jenkins? Perhaps the Citrix environment > > > > already supports something like this via Jenkins API? > > > > > > > > -- > > Prasanna., > > > > ------------------------ > > Powered by BigRock.com > > > > -- Prasanna., ------------------------ Powered by BigRock.com
