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

[Karel Piwko]

On Mon, 15 Jul 2013 12:50:35 -0500
Kris Borchers <kris at 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 at 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 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
> > _______________________________________________
> > 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