[jboss-jira] [JBoss JIRA] (AS7-4432) Run AS 7 testsuite on OpenShift

Mon Apr 16 03:28:18 EDT 2012

    [ https://issues.jboss.org/browse/AS7-4432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12684351#comment-12684351 ] 

Ondrej Zizka commented on AS7-4432:
-----------------------------------

(10:08:32 PM) OndraZizka: aslak:  Have you tried openshift?
(10:08:45 PM) OndraZizka: And arq in it's commit-hook build?
(10:08:58 PM) OndraZizka: Gotta go now, but will read your answer later. Thanks!
(10:11:41 PM) aslak: OndraZizka, i haven't tried it as part of the build by using a managed container. doubt that will work
(10:12:09 PM) aslak: but using a openshift account to run test in openshift from the client works
(10:12:21 PM) aslak: and the same can be done via jenkins on openshift
(10:12:32 PM) aslak: using the arq-openshift express container
(11:51:44 PM) OndraZizka: aslak, great!
(11:52:13 PM) OndraZizka: aslak:  It's one of my future goal, to check what would need to be done to make managed  cont. work
(11:52:36 PM) OndraZizka: So far it's blocked by due to inaccessible mgmt api
(11:53:12 PM) OndraZizka: Which is probably intentional feature, not technical lack
(11:59:57 PM) aslak: OndraZizka, you can't use the AS7 Managed apis during test on OpenShift deploy.. 
(04/16/2012 12:00:18 AM) aslak: in theory you might get it to run on the instance b yauto extract etc and changing all ports bla bla.. 
(12:00:25 AM) aslak: but you probably want to look at this: http://arquillian.org/modules/openshift-express-container-adapter/
(12:00:56 AM) aslak: then have two apps.. your production, your test app and your jenkins instance
(12:01:21 AM) aslak: deploy to prod, cause a jenkins build, which test against your test app before production is updated
(12:03:28 AM) OndraZizka: aslak: This is a special case - 
(12:03:46 AM) OndraZizka: I'd like to run the testsuite, at least smoke and basic, against OS
(12:04:21 AM) aslak: the as7 suite ? 
(12:04:24 AM) OndraZizka: Yes
(12:04:28 AM) OndraZizka: But I  understand that 
(12:04:45 AM) aslak: OpenShift only support the Servlet protocol.. 
(12:04:55 AM) OndraZizka: Huh.
(12:05:14 AM) aslak: and OpenShift has no proper mgm api, so we introspect the Archive to fogure out contexts etc.. 
(12:05:21 AM) aslak: figure
(12:05:30 AM) OndraZizka: hmm...
(12:05:37 AM) sannegrinovero left the room (quit: Quit: Leaving).
(12:06:05 AM) OndraZizka: aslak:  Have you talked about this with OS devs?
(12:06:16 AM) OndraZizka: Perhaps some plans for mgmt support on their side?
(12:06:44 AM) aslak: yea, there has been some talk about it.. 
(12:08:12 AM) aslak: hmm.. 
(12:08:29 AM) aslak: we do have a ping we deploy to know when the deployment is actually deployed.. 
(12:09:01 AM) aslak: not sure why we didn't think of returning the contexts etc in the same call
(12:09:05 AM) aslak: that could be done
(12:09:21 AM) aslak: at least we get the 'real' deployment context and can drop the archive scanning locally
(12:17:05 AM) aslak: but still, in the current state, open shift does not support AS7-JMX protocol, which means no Service to call which gives access to internals
(12:17:30 AM) aslak: but anything that only need EE apis should work via the Servlet Protocol

> Run AS 7 testsuite on OpenShift
> -------------------------------
>
>                 Key: AS7-4432
>                 URL: https://issues.jboss.org/browse/AS7-4432
>             Project: Application Server 7
>          Issue Type: Task
>          Components: Test Suite
>            Reporter: Ondrej Zizka
>            Assignee: Ondrej Zizka
>            Priority: Minor
>             Fix For: No Release
>
>
> What steps OpenShift does:
> 1) Calls the pre-build hook
> 2) Calls the build hook
> 3) Builds the project, with quite low timeout, using {{mvn -e clean package -Popenshift -DskipTests}}
> 4) Calls the deploy hook
> 5) Deploys
> 6) Calls the post-deploy hook
> * Want to test the OpenShift's AS instance.
> * Running the AS build will download the dependencies.
> * The question is, whether during post-deploy we have the local repo at hand.
> * In the post-deploy hook, we will run the testsuite against the AS instance.
> * To do that, we will use the {{allowConnectingToRunningServer}} Arquillian param.
> * We will need to override the {{-DskipTests}}.
> Things to use:
> * Configure AS: {{.openshift/config/standalone.xml}}
> * Deploy pre-built app:  {{git add deployments/my-app.war}}
> Vojta suggested we could connect the OS AS server as a Jenkins cartridge slave, and run the tests against it while having it as local, i.e. managed, AS instance.
> BZ: https://bugzilla.redhat.com/show_bug.cgi?id=810946
> Our OpenShift contact:  Bill DeCoste, bdecoste @ #libra IRC

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira