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

Well keeping the idea of Karel of deploying "at build time" could we not think about a nodejs backend dedicated to the integration tests deployed on OS at each build ? On Mon, Jul 15, 2013 at 6:15 PM, Kris Borchers <kris(a)redhat.com&gt; wrote: On Jul 15, 2013, at 11:08 AM, Summers Pittman <supittma(a)redhat.com&gt; 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(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev