-
New Feature
-
Resolution: Fixed
-
Major
-
-
Pipeline - July/August, Pipeline - December
JUnit test result archiving can happen multiple times inside workflow, and currently there's no way to meaningfully distinguish multiple invocations.
- is blocked by
-
JENKINS-53362 Update documentation for junit Pipeline step return value
- Open
- is blocking
-
JENKINS-41031 in Junit reports wrong output is shown for tests with same name
- Closed
-
JENKINS-45826 XUnit support for distinguishing test reports from different steps
- Resolved
-
JENKINS-35420 Realtime junit report to support Pipeline (was: throws ClassCastException when pipeline run)
- Resolved
- is duplicated by
-
JENKINS-41031 in Junit reports wrong output is shown for tests with same name
- Closed
-
JENKINS-41855 Add an label to Junit test report in Pipeline
- Resolved
-
JENKINS-41710 Annotate test results with a test run name
- Closed
- is related to
-
JENKINS-26107 Allow stage to operate as a labelled block
- Closed
-
JENKINS-48020 Warning log spam "[hudson.tasks.junit.CaseResult getRun] In getOwner(), suiteResult.getParent() is null."
- Resolved
-
JENKINS-26522 Annotated block/stage status
- Closed
-
JENKINS-36932 Add a "matrix" step to workflow-basic-steps
- Resolved
- relates to
-
JENKINS-46166 Distingush tests by stage and parallel
- Resolved
-
JENKINS-40986 Matrix structure for Declarative Pipeline
- Resolved
-
JENKINS-39353 Include filtering by class name when splitting tests
- Closed
- links to
- mentioned in
-
Page Loading...