<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Again, I don't want to wait on that long deploy process during a build. We should not have to work around this. It should just work. If I have an app on OpenShift, I should be able to test against it.<div><br><div><div>On Jul 15, 2013, at 11:24 AM, Sebastien Blanc <<a href="mailto:scm.blanc@gmail.com">scm.blanc@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">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 ? <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"><<a href="mailto:kris@redhat.com" target="_blank">kris@redhat.com</a>></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 <<a href="mailto:supittma@redhat.com">supittma@redhat.com</a>> wrote:<br>
<br>
> On 07/15/2013 11:36 AM, Karel Piwko wrote:<br>
>> Hi,<br>
>><br>
>> one of the possible ways how to fix OpenShift cartridge going idle could be<br>
>> fixed by deploying the backend to the cartridge right before tests. That way<br>
>> it would be fresh when running tests.<br>
>><br>
>> There is already tooling almost exactly what we need. However, it<br>
>> would "polute" Aerogear JS with some WAR or whatever Kris needs to be deployed.<br>
>><br>
>> WDYT?<br>
> Couldn't this be done with the travis build scripts and have it<br>
> 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">>><br>
>> Karel<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>
><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>
<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>
_______________________________________________<br>aerogear-dev mailing list<br><a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/aerogear-dev</blockquote></div><br></div></body></html>