[
https://issues.jboss.org/browse/WFLY-12503?page=com.atlassian.jira.plugin...
]
Brian Stansberry edited comment on WFLY-12503 at 9/7/19 12:43 PM:
------------------------------------------------------------------
This is problematic for -Delytron because for some reason adding the profile to the root
pom adjusting the surefire plugin execution causes the execution of various
'process-test-resource' phase maven goals to happen in a different order. The
testsuite/integration/elytron module has a number of such goals and reordering them breaks
the ultimately configuration against which the tests run, leading to failures.
Breaking out the -Dsecurity.manager commit into a separate JIRA/PR would get the benefit
of that bit, but I have other priorities so I'm putting this on the shelf for now.
was (Author: brian.stansberry):
This is problematic for -Delytron because for some reason adding the profile to the root
pom adjusting the surefire plugin execution causes the execution of various
'process-test-resource' phase maven goals to happen in a different order. The
testsuite/integration/elytron module has a number of such goals and reordering them breaks
the ultimately configuration against which the tests run, leading to failures.
Turn off the default surefire execution when the 'elytron'
and 'security.manager' profiles are used
---------------------------------------------------------------------------------------------------
Key: WFLY-12503
URL:
https://issues.jboss.org/browse/WFLY-12503
Project: WildFly
Issue Type: Task
Components: Test Suite
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Priority: Major
We have CI runs for PRs that differ from the basic ones by using -Delytron instead of
-DallTests to turn on profiles that select a subset of the testsuite and to specially
configure things for that subset. Same for -Dsecurity.manager.
Expand on this by having -Delytron and -Dsecurity.manager also turn on profiles that turn
off the default surefire execution, so surefire only runs for those maven modules where a
profile turns it back on. There's no point, for example, running the
'undertow' maven module tests in these CI runs.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)