[
https://issues.jboss.org/browse/WFLY-8415?page=com.atlassian.jira.plugin....
]
Tomaz Cerar moved JBEAP-9750 to WFLY-8415:
------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-8415 (was: JBEAP-9750)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Build System
Test Suite
(was: Build System)
Affects Version/s: (was: 7.1.0.DR12)
Remove Elytron integration tests module from default build chain
----------------------------------------------------------------
Key: WFLY-8415
URL:
https://issues.jboss.org/browse/WFLY-8415
Project: WildFly
Issue Type: Task
Components: Build System, Test Suite
Reporter: Tomaz Cerar
Assignee: Tomaz Cerar
Elytron module is always part of the build chain now. We use separate jobs to run unit
tests, integration tests and mixed domain tests and Elytron integration tests are now run
in all of them.
e.g. command we use to run just unit tests {{mvn test -DskipTests -Dts.noSmoke}} now
starts also Elytron module (same goes to mixed domain, domain and others).
Elytron integration module should behave as other test suite modules - be part of
{{all-modules.module.profile}} profile, have its own {{elytron.module.profile}} with
{{ts.elytron}} activation property.
see
http://pastebin.test.redhat.com/457432
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)