<div dir="ltr">Well keeping the idea of Karel of deploying &quot;at build time&quot; could we not think about a nodejs backend dedicated to the integration tests deployed on OS  at each build ? <div> </div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Mon, Jul 15, 2013 at 6:15 PM, Kris Borchers <span dir="ltr">&lt;<a href="mailto:kris@redhat.com" target="_blank">kris@redhat.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><br>
On Jul 15, 2013, at 11:08 AM, Summers Pittman &lt;<a href="mailto:supittma@redhat.com">supittma@redhat.com</a>&gt; wrote:<br>
<br>
&gt; On 07/15/2013 11:36 AM, Karel Piwko wrote:<br>
&gt;&gt; Hi,<br>
&gt;&gt;<br>
&gt;&gt; one of the possible ways how to fix OpenShift cartridge going idle could be<br>
&gt;&gt; fixed by deploying the backend to the cartridge right before tests. That way<br>
&gt;&gt; it would be fresh when running tests.<br>
&gt;&gt;<br>
&gt;&gt; There is already tooling almost exactly what we need. However, it<br>
&gt;&gt; would &quot;polute&quot; Aerogear JS with some WAR or whatever Kris needs to be deployed.<br>
&gt;&gt;<br>
&gt;&gt; WDYT?<br>
&gt; Couldn&#39;t this be done with the travis build scripts and have it<br>
&gt; clone/publish a project/war from somewhere else?<br>
<br>
</div>The problem is I am running these integration tests via local builds, not just on Travis so that will not work.<br>
<div class="HOEnZb"><div class="h5">&gt;&gt;<br>
&gt;&gt; Karel<br>
&gt;&gt; _______________________________________________<br>
&gt;&gt; aerogear-dev mailing list<br>
&gt;&gt; <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
&gt;&gt; <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; aerogear-dev mailing list<br>
&gt; <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
&gt; <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
<br>
<br>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
</div></div></blockquote></div><br></div>