[aerogear-dev] Idea: Create OpenShift cartridge for AGJS testing during tests

[Karel Piwko]

Local builds can skip that part, OS deployment triggered in Travis only.

Alternatively,you could supply your ssh key/credentials to deploy backend in cartridge you own.

Sent from my Android phone using TouchDown (www.nitrodesk.com)


-----Original Message-----
From: Kris Borchers [kris at redhat.com]
Received: Monday, 15 Jul 2013, 18:15
To: AeroGear Developer Mailing List [aerogear-dev at lists.jboss.org]
Subject: Re: [aerogear-dev] Idea: Create OpenShift cartridge for AGJS	testing during tests



On Jul 15, 2013, at 11:08 AM, Summers Pittman <supittma at redhat.com> wrote:

> On 07/15/2013 11:36 AM, Karel Piwko wrote:
>> Hi,
>> 
>> one of the possible ways how to fix OpenShift cartridge going idle could be
>> fixed by deploying the backend to the cartridge right before tests. That way
>> it would be fresh when running tests.
>> 
>> There is already tooling almost exactly what we need. However, it
>> would "polute" Aerogear JS with some WAR or whatever Kris needs to be deployed.
>> 
>> WDYT?
> Couldn't this be done with the travis build scripts and have it 
> clone/publish a project/war from somewhere else?

The problem is I am running these integration tests via local builds, not just on Travis so that will not work.
>> 
>> Karel
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
> 
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev


_______________________________________________
aerogear-dev mailing list
aerogear-dev at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev