Hi,
I am currently looking at using a Jenkinsfile instead of manually creating
jobs with the view of moving forward with the multi pipeline approach of
doing jobs. However there seems to be a limitation in the Jenkinsfile that
I can't seem to get around.
I currently have two jobs that use the same branch and the build execute
steps are almost the same apart from one passes a "--skip" flag to the test
code.
So I have one job that runs all tests and tracks when known failures are
finally fixed. The second job runs all of the tests that are known to fail.
If this job fails then t hat is a regression and all work must stop to fix
this.
I have tried the following approach with a Jenkinsfile
node {
stage 'Build'
checkout scm
stage 'Test'
try {
sh './runtests all'
} catch (e) {
//currentBuild.result = 'FAILURE'
}
archive 'all.xml'
step([$class: 'JUnitResultArchiver', testResults: all.xml'])
stage 'TestSkipFailures'
try {
sh './runtests skip'
} catch (e) {
currentBuild.result = 'FAILURE'
}
archive 'skip.xml'
step([$class: 'JUnitResultArchiver', testResults: 'skip.xml'])
stage 'Cleanup'
sh 'git clean -fdx'
}
However as the generated xml has the same class names only one is
processed. What I want to be able to do is have two graphs tracking all
tests and skipped tests at the same time, just like I could with the two
separate jobs. Is this possible just using a Jenkinsfile?
Kind regards, Ian
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/c9f77b15-266c-4c17-8ee7-237d80c8c04d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
