[Red Hat JIRA] (WFLY-14223) Support for tracing db calls
by Tobias Stadler (Jira)
Tobias Stadler created WFLY-14223:
-------------------------------------
Summary: Support for tracing db calls
Key: WFLY-14223
URL: https://issues.redhat.com/browse/WFLY-14223
Project: WildFly
Issue Type: Feature Request
Components: MP OpenTracing
Reporter: Tobias Stadler
Assignee: Emmanuel Hugonnet
WildFly should support tracing sh calls on managed datasourves (creating spans) similar to Microprofile Rest Client.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[Red Hat JIRA] (WFLY-14222) Support for tracing jms messages
by Tobias Stadler (Jira)
Tobias Stadler created WFLY-14222:
-------------------------------------
Summary: Support for tracing jms messages
Key: WFLY-14222
URL: https://issues.redhat.com/browse/WFLY-14222
Project: WildFly
Issue Type: Feature Request
Components: MP OpenTracing
Reporter: Tobias Stadler
Assignee: Emmanuel Hugonnet
WildFly should support tracing sending/receiving JMS messages (creating spans, propagating the trace id) similar to Microprofile Rest Client.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[Red Hat JIRA] (WFLY-12503) Turn off the default surefire execution when the 'elytron', 'security.manager' and 'bootable.jar' profiles are used
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-12503?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFLY-12503:
------------------------------------
Summary: Turn off the default surefire execution when the 'elytron', 'security.manager' and 'bootable.jar' profiles are used (was: Turn off the default surefire execution when the 'elytron' and 'security.manager' profiles are used)
> Turn off the default surefire execution when the 'elytron', 'security.manager' and 'bootable.jar' profiles are used
> -------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-12503
> URL: https://issues.redhat.com/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.8#713008)
5 years, 7 months
[Red Hat JIRA] (WFLY-12503) Turn off the default surefire execution when the 'elytron', 'security.manager' and 'bootable.jar' profiles are used
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-12503?page=com.atlassian.jira.plugi... ]
Brian Stansberry updated WFLY-12503:
------------------------------------
Description:
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 and -Dts.bootable.
Expand on this by having -Delytron, -Dsecurity.manager and -Dts.bootable 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.
was:
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.
> Turn off the default surefire execution when the 'elytron', 'security.manager' and 'bootable.jar' profiles are used
> -------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-12503
> URL: https://issues.redhat.com/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 and -Dts.bootable.
> Expand on this by having -Delytron, -Dsecurity.manager and -Dts.bootable 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.8#713008)
5 years, 7 months