-
Improvement
-
Resolution: Duplicate
-
Minor
-
None
-
Jenkins 2.44
Currently in our pipeline we are running different set of tests, each of them will produce a few thousands of Junit XML test reports.
If we are using junit "*/TEST-.xml" to archive those test reports, all of the test results will be aggregated into one test report (Under 'All Tests')
It would be more user-friendly if we can add an label when we are archiving junit test reports.
Possible syntax: see attachment
and it will produce two junit test report in the "Test Result" tab, one for server tests, and one for ui tests (see attachment 2)
- duplicates
-
JENKINS-27395 distinguish test reports filed from different parts of workflow
-
- Resolved
-
[JENKINS-41855] Add an label to Junit test report in Pipeline
Description |
Original:
Currently in our pipeline we are running different set of tests, each of them will produce a few thousands of Junit XML test reports. If we are using junit "**/TEST-*.xml" to archive those test reports, all of the test results will be aggregated into one test report (Under 'All Tests') It would be more user-friendly if we can add an label when we are archiving junit test reports. such as node ('worker') { stage('server test') test() junit "server/results/Test-*.xml", label 'server tests' stage(ui test) test() junit "ui/results/Test-*.xml", label 'ui tests' } and it will produce two junit test report in the "Test Result" tab, one for server tests, and one for ui tests |
New:
Currently in our pipeline we are running different set of tests, each of them will produce a few thousands of Junit XML test reports. If we are using junit "**/TEST-*.xml" to archive those test reports, all of the test results will be aggregated into one test report (Under 'All Tests') It would be more user-friendly if we can add an label when we are archiving junit test reports. such as node ('worker') { stage('server test') test() junit "server/results/Test-*.xml", label 'server tests' stage(ui test) test() junit "ui/results/Test-*.xml", label 'ui tests' } and it will produce two junit test report in the "Test Result" tab, one for server tests, and one for ui tests |
Description |
Original:
Currently in our pipeline we are running different set of tests, each of them will produce a few thousands of Junit XML test reports. If we are using junit "**/TEST-*.xml" to archive those test reports, all of the test results will be aggregated into one test report (Under 'All Tests') It would be more user-friendly if we can add an label when we are archiving junit test reports. such as node ('worker') { stage('server test') test() junit "server/results/Test-*.xml", label 'server tests' stage(ui test) test() junit "ui/results/Test-*.xml", label 'ui tests' } and it will produce two junit test report in the "Test Result" tab, one for server tests, and one for ui tests |
New:
Currently in our pipeline we are running different set of tests, each of them will produce a few thousands of Junit XML test reports. If we are using junit "**/TEST-*.xml" to archive those test reports, all of the test results will be aggregated into one test report (Under 'All Tests') It would be more user-friendly if we can add an label when we are archiving junit test reports. such as node ('worker') { stage('server test') test() junit "server/results/Test-*.xml", label 'server tests' stage(ui test) test() junit "ui/results/Test-*.xml", label 'ui tests' } and it will produce two junit test report in the "Test Result" tab, one for server tests, and one for ui tests |
Component/s | New: pipeline-build-step-plugin [ 21707 ] |
Description |
Original:
Currently in our pipeline we are running different set of tests, each of them will produce a few thousands of Junit XML test reports. If we are using junit "**/TEST-*.xml" to archive those test reports, all of the test results will be aggregated into one test report (Under 'All Tests') It would be more user-friendly if we can add an label when we are archiving junit test reports. such as node ('worker') { stage('server test') test() junit "server/results/Test-*.xml", label 'server tests' stage(ui test) test() junit "ui/results/Test-*.xml", label 'ui tests' } and it will produce two junit test report in the "Test Result" tab, one for server tests, and one for ui tests |
New:
Currently in our pipeline we are running different set of tests, each of them will produce a few thousands of Junit XML test reports. If we are using junit "**/TEST-*.xml" to archive those test reports, all of the test results will be aggregated into one test report (Under 'All Tests') It would be more user-friendly if we can add an label when we are archiving junit test reports. such as {quote} node ('worker') { stage('server test') test() junit "server/results/Test-*.xml", label 'server tests' stage(ui test) test() junit "ui/results/Test-*.xml", label 'ui tests' } {quote} and it will produce two junit test report in the "Test Result" tab, one for server tests, and one for ui tests |
Description |
Original:
Currently in our pipeline we are running different set of tests, each of them will produce a few thousands of Junit XML test reports. If we are using junit "**/TEST-*.xml" to archive those test reports, all of the test results will be aggregated into one test report (Under 'All Tests') It would be more user-friendly if we can add an label when we are archiving junit test reports. such as {quote} node ('worker') { stage('server test') test() junit "server/results/Test-*.xml", label 'server tests' stage(ui test) test() junit "ui/results/Test-*.xml", label 'ui tests' } {quote} and it will produce two junit test report in the "Test Result" tab, one for server tests, and one for ui tests |
New:
Currently in our pipeline we are running different set of tests, each of them will produce a few thousands of Junit XML test reports. If we are using junit "**/TEST-*.xml" to archive those test reports, all of the test results will be aggregated into one test report (Under 'All Tests') It would be more user-friendly if we can add an label when we are archiving junit test reports. node ('worker') { stage('server test') test() junit "server/results/Test-*.xml", label 'server tests' stage(ui test) test() junit "ui/results/Test-*.xml", label 'ui tests' } and it will produce two junit test report in the "Test Result" tab, one for server tests, and one for ui tests |
Attachment | New: screenshot-1.png [ 35836 ] |
Description |
Original:
Currently in our pipeline we are running different set of tests, each of them will produce a few thousands of Junit XML test reports. If we are using junit "**/TEST-*.xml" to archive those test reports, all of the test results will be aggregated into one test report (Under 'All Tests') It would be more user-friendly if we can add an label when we are archiving junit test reports. node ('worker') { stage('server test') test() junit "server/results/Test-*.xml", label 'server tests' stage(ui test) test() junit "ui/results/Test-*.xml", label 'ui tests' } and it will produce two junit test report in the "Test Result" tab, one for server tests, and one for ui tests |
New:
Currently in our pipeline we are running different set of tests, each of them will produce a few thousands of Junit XML test reports. If we are using junit "**/TEST-*.xml" to archive those test reports, all of the test results will be aggregated into one test report (Under 'All Tests') It would be more user-friendly if we can add an label when we are archiving junit test reports. Possible syntax: see attachment and it will produce two junit test report in the "Test Result" tab, one for server tests, and one for ui tests |
Attachment | New: screenshot-2.png [ 35837 ] |
Description |
Original:
Currently in our pipeline we are running different set of tests, each of them will produce a few thousands of Junit XML test reports. If we are using junit "**/TEST-*.xml" to archive those test reports, all of the test results will be aggregated into one test report (Under 'All Tests') It would be more user-friendly if we can add an label when we are archiving junit test reports. Possible syntax: see attachment and it will produce two junit test report in the "Test Result" tab, one for server tests, and one for ui tests |
New:
Currently in our pipeline we are running different set of tests, each of them will produce a few thousands of Junit XML test reports. If we are using junit "**/TEST-*.xml" to archive those test reports, all of the test results will be aggregated into one test report (Under 'All Tests') It would be more user-friendly if we can add an label when we are archiving junit test reports. Possible syntax: see attachment and it will produce two junit test report in the "Test Result" tab, one for server tests, and one for ui tests (see attachment 2) |
Link |
New:
This issue duplicates |
Resolution | New: Duplicate [ 3 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |