allure2 icon indicating copy to clipboard operation
allure2 copied to clipboard

History not shown correctly when using concurrent builds from Jenkins

Open danalbu opened this issue 7 years ago • 2 comments

I'm submitting a ...

  • [x] bug report
  • [ ] feature request
  • [ ] support request => Please do not submit support request here, see note at the top of this template.

What is the current behavior?

The history feature is not showing the correct history when using Jenkins concurrent builds. Some of the jobs are skipped from the history.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

  1. Configure Jenkins job as follows:
  • Jenkins multimodule (matrix) with 1 configuration only
  • Limit to 10 max # builds to keep
  • Add concurrent builds option
  • Limit concurrent builds to 4
  • Trigger 4 builds x 2 then the last 2 for a total of 10

What is the expected behavior?

The history trend should show all 10 jobs in order from 1 to 10 for the last report generated by the job

What is the motivation / use case for changing the behavior?

Please tell us about your environment:

Allure version 2.4.1
Test framework any
Allure adaptor any
Generate report using any

Other information

The same "bug" reproduces when going to the individual test history tab. E.g.:

  • Build number 8
  • History shows trend for 8/7/4/3/2/1
  • Test individual history shows only 8/7/4 (i know about the 5 limit)

I hope i am not the only one having this issue.

danalbu avatar Oct 30 '17 10:10 danalbu

Hi . I think behavior is the same. I use allure jenkins plugin. When I use the option "Execute concurrent builds if necessary" to run parallel the the report generates in

Report successfully generated to ~/.jenkins/workspace/Appium@4/allure-report or Appium@3 , Appium@2 etc and nothing appear in report. Is there a way to combine Appium@4 , Appium@3 etc folder reports into ~/.jenkins/workspace/Appium/allure-report

pargev avatar Dec 20 '17 11:12 pargev

Is anyone able to find a solution to this issue? The same issue happens on Jenkins Pipeline Matrix projects.

velzganesh avatar Jul 21 '22 05:07 velzganesh