5:36 p.m.
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?
Karel
5:59 p.m.
To me sounds like a huge trade-off if "polute" AeroGear JS is required.
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?
--
abstractj
6:06 p.m.
-- for polluting.
On Jul 15, 2013, at 11:59 AM, Bruno Oliveira <bruno(a)abstractj.org> wrote:
To me sounds like a huge trade-off if "polute" AeroGear JS
is required.
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?
--
abstractj
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
6:15 p.m.
AeroGear.js will NEVER have a WAR or anything of that sort in it.
On Jul 15, 2013, at 10:59 AM, Bruno Oliveira <bruno(a)abstractj.org> wrote:
To me sounds like a huge trade-off if "polute" AeroGear JS
is required.
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?
--
abstractj
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
6:08 p.m.
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?
Karel
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
6:15 p.m.
On Jul 15, 2013, at 11:08 AM, Summers Pittman <supittma(a)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(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
6:24 p.m.
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> wrote:
On Jul 15, 2013, at 11:08 AM, Summers Pittman <supittma(a)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(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
7:22 p.m.
Exactly,thanks Sebi.
I made original statement wrong. I should not have written WAR but backend.Ofc it can be
node.js,fits the story much better.
Sent from my Android phone using TouchDown (www.nitrodesk.com)
-----Original Message-----
From: Sebastien Blanc [scm.blanc(a)gmail.com]
Received: Monday, 15 Jul 2013, 18:25
To: AeroGear Developer Mailing List [aerogear-dev(a)lists.jboss.org]
Subject: 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> wrote:
On Jul 15, 2013, at 11:08 AM, Summers Pittman <supittma(a)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(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
7:23 p.m.
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.
On Jul 15, 2013, at 11:24 AM, Sebastien Blanc <scm.blanc(a)gmail.com> wrote:
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> wrote:
On Jul 15, 2013, at 11:08 AM, Summers Pittman <supittma(a)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(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
7:27 p.m.
New subject: Idea: Create OpenShift cartridge for AGJS testing during tests
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(a)redhat.com]
Received: Monday, 15 Jul 2013, 18:15
To: AeroGear Developer Mailing List [aerogear-dev(a)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(a)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(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
7:50 p.m.
New subject: Idea: Create OpenShift cartridge for AGJS testing during tests
The problem though is I want the integration tests to run on every build, whether it's
local or inTravis. I don't want to manage two separate processes for that so I need
this to work without an OS deployment for every build no matter where it's at.
On Jul 15, 2013, at 12:27 PM, Karel Piwko <kpiwko(a)redhat.com> wrote:
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(a)redhat.com]
Received: Monday, 15 Jul 2013, 18:15
To: AeroGear Developer Mailing List [aerogear-dev(a)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(a)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(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
10:06 a.m.
On Mon, 15 Jul 2013 12:50:35 -0500
Kris Borchers <kris(a)redhat.com> wrote:
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.
Yes, the long deploy should be a part of CI only. AIUI, this is not a
workaround. OS app will get idle sooner or later no matter the time limit.
The problem though is I want the integration tests to run on every
build,
whether it's local or inTravis. I don't want to manage two separate processes
for that so I need this to work without an OS deployment for every build no
matter where it's at.
I don't see two processes here. My understanding is that you prepare the backend
on OS and run integration tests while running locally. What I'm proposing is to
prepare the backend on OS as a part of CI as well.
And you can surely run this as a part of before_script in Travis. All you need
is a backend to be on GH, encrypted SSH key to access OS in Travis and a
simple scp script.
On Jul 15, 2013, at 12:27 PM, Karel Piwko <kpiwko(a)redhat.com> wrote:
> 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(a)redhat.com]
> Received: Monday, 15 Jul 2013, 18:15
> To: AeroGear Developer Mailing List [aerogear-dev(a)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(a)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(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
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
4203
days inactive
4204
days old
11 comments
6 participants
participants (6)
-
Bruno Oliveira -
Karel Piwko -
Kris Borchers -
Lucas Holmquist -
Sebastien Blanc -
Summers Pittman