Strategic fix for allure report generation memory issues (#5845)

This commit is contained in:
Ramzi El-Yafi 2020-01-14 11:10:42 +00:00
parent b512a2981d
commit 9ae60a934c

View File

@ -65,22 +65,13 @@ pipeline {
* copied to avoid collisions between files where the same test * copied to avoid collisions between files where the same test
* classes have run on multiple pods. * classes have run on multiple pods.
*/ */
sh label: 'Compact test results', fileOperations([fileCopyOperation(
script: includes: '**/test-results-xml/**/test-runs/test-reports/**',
'''#!/bin/bash targetLocation: 'allure-input',
shopt -s globstar flattenFiles: true,
rm -rf allure-input renameFiles: true,
mkdir allure-input sourceCaptureExpression: '.*test-results-xml/.*-([\\d]+)/.*/([^/]+)$',
targetNameExpression: '$1-$2')])
for i in **/test-results-xml/**/test-runs/test-reports/**
do
[ -f $i ] &&
cp $i allure-input/$(echo $i | sed -e \\
\'s/.*test-results-xml\\/.*-\\(.*\\)\\/test-runs\\/.*\\/\\(.*\\)$/\\1\\-\\2/\')
done
echo "Finished compacting JUnit results"
'''
allure includeProperties: false, allure includeProperties: false,
jdk: '', jdk: '',
results: [[path: '**/allure-input']] results: [[path: '**/allure-input']]