0

My allure reports are growing in size running the same test against the same build. Here is the kicker which is blowing my mind on how this could be happening. The VM that is running the test and producing the allure report is reverted from a clean state snapshot at the beginning of each test run and the report is generated in the Jenkins workspace which is also cleared at the beginning of each test run so there is no possible way anything is left over from previous test runs or report generations. Report sizes for same exact test against same build... enter image description here

My report generation block from Jenkins pipeline using the Allure Plugin...

allure([

includeProperties: false,
jdk: '',
properties: [],
reportBuildPolicy: 'ALWAYS',
results: [[path: "$env.BUILD_NUMBER"]]

])

Question: is there some properties to include that will force a clean report with no history in it?
Please advise if you can help

Improve this question
2
  • Here are the sizes for the same test against same build... Test# Tests Size 7 cAPI 74487489 8 cAPI 75102951 9 cAPI 75406772 10 cAPI 75546201 11 cAPI 75807553 Commented Apr 2 at 19:35
  • Hello, do you mind formatting the attached image? Also, no need to be super polite, this website is Wiki style Commented Apr 9 at 1:36
Related questions
3
Access allure reports while test is running
3
Build step 'Allure Report' changed build result to UNSTABLE
2
Allure Jenkins behave BDD report generating blank report
Load 5 more related questions Show fewer related questions

0

Reset to default

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.