[JBoss JIRA] (RTGOV-486) Align deployment targets with other overlord sub-projects
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/RTGOV-486?page=com.atlassian.jira.plugin.... ]
Gary Brown commented on RTGOV-486:
----------------------------------
Most places have been changed to reflect the target.
Currently samples are still split as jbossas and karaf. As more platforms are supported, may need to rethink this.
Ant script now used at top level, with the platform using consistent names for the targets.
> Align deployment targets with other overlord sub-projects
> ---------------------------------------------------------
>
> Key: RTGOV-486
> URL: https://issues.jboss.org/browse/RTGOV-486
> Project: RTGov (Run Time Governance)
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Gary Brown
> Assignee: Gary Brown
> Fix For: 2.0.0.Final
>
>
> Change deployment targets to be consistent with other overlord sub-projects. For example, instead of jbossas, it should be eap6 (or eap61/63 if split required), and fuse61 instead of karaf - although support for Karaf will also be required.
> As part of this change, change the deployment approach to use ant script at top level, instead of maven - again for consistency with sramp/dtgov. Quickstarts could still use maven, unless deployment across targets is more consistent with ant.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 2 months
[JBoss JIRA] (SRAMP-431) Arquillian-based integration tests
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-431?page=com.atlassian.jira.plugin.... ]
Brett Meyer updated SRAMP-431:
------------------------------
Git Pull Request: https://github.com/Governance/s-ramp/pull/457
> Arquillian-based integration tests
> ----------------------------------
>
> Key: SRAMP-431
> URL: https://issues.jboss.org/browse/SRAMP-431
> Project: S-RAMP
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Brett Meyer
> Assignee: Brett Meyer
> Fix For: 0.6.0
>
>
> Create a new s-ramp-test module to contain all integration tests. Thoughts:
> - 1 central ant script, executed by the POM, should be in charge of downloading the Jetty and and Tomcat distros, then unpacking them. Arquillian would then use them in a "managed mode."
> - The ant script will eventually be in charge of downloading EAP as well, but not until we have CI hardware within the RH network. Until then, we'll need to do something similar to RTGov's current tests: require the distro be manually downloaded and unpacked, then set $JBOSS_HOME
> - Fuse should be run in embedded mode.
> - No tests should run by default. Hide all behind container-specific profiles, enabled only on the CI job(s).
> - Include a simple s-ramp-client based test to at least ensure the app comes up, auth works, and uploading/querying works.
> - Pull in any functional tests from the other modules requiring the server to be spun-up. Leave behind only pure *unit* tests.
> The work-in-progress: https://github.com/brmeyer/s-ramp/compare/integration-tests
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 2 months
[JBoss JIRA] (SRAMP-459) Integration tests: Jetty
by Brett Meyer (JIRA)
[ https://issues.jboss.org/browse/SRAMP-459?page=com.atlassian.jira.plugin.... ]
Brett Meyer commented on SRAMP-459:
-----------------------------------
I'm deferring this for now. Arquillian does not have a Jetty 8 container (only 7 & 9). Further, embedded mode is the only option. I'm not sure if Jetty has the capacity to be run in a managed mode, period. If it's determined that there would be enough value in this to make it worth the effort, significant portions of s-ramp-dev-server could be reused, conceptually.
But, since Tomcat is fully tested, ignoring Jetty altogether might be "good enough."
> Integration tests: Jetty
> ------------------------
>
> Key: SRAMP-459
> URL: https://issues.jboss.org/browse/SRAMP-459
> Project: S-RAMP
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Brett Meyer
> Assignee: Brett Meyer
>
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 2 months