Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Allure report history trend vs Jenkins' allure history trend #215

Closed
hoopy728 opened this issue Aug 17, 2018 · 13 comments
Closed

Allure report history trend vs Jenkins' allure history trend #215

hoopy728 opened this issue Aug 17, 2018 · 13 comments

Comments

@hoopy728
Copy link

hoopy728 commented Aug 17, 2018 •
edited
Loading

Issue

The Allure report history trend colour is not the same as per Jenkins' Allure history trend. Is there any properties file that can configure the colour code type?

Context

  • Jenkins version: 2.7.8

  • Job type: Maven

  • Allure plugin version: 2.6.1

  • Allure commandline version: -

Problem description

Following are the history trend view via Allure report and Jenkins. As you can see the product defect is red in Allure report history but yellow in Jenkins history trend. I'm trying to sync the same colour toward Jenkins Allure history trend.

Allure report's history trend
image

Jenkins' Allure history trend
image
@baev baev mentioned this issue Jan 15, 2019
Closed
3 tasks
@goatsy
Copy link

goatsy commented Feb 12, 2019

Is there a fix for this behaviour?

@Agentbars
Copy link

Will that be fixed?

Thanks)

@iridiculous
Copy link

Can we get at least a comment here to know whether this gets fixed / if theres a workaround ?
This is totally misleading

@abaradulkin
Copy link

Vote for this issue!

@borbamartin
Copy link

borbamartin commented Oct 8, 2019 •
edited
Loading

+1. Failed tests are represented as broken in the Jenkins trend chart

@iklimchuk
Copy link

+1

@dwells-ancoris
Copy link

Any update on this?

@timbi4
Copy link

timbi4 commented Jan 15, 2021

Failed tests are represented as broken in the Jenkins trend chart

@guzy0324
Copy link

I encountered the same problem

@amdas383
Copy link

Any update on this issue

@soul3510
Copy link

soul3510 commented Jan 4, 2023

I also encountered the same issue version 2.19.0

@cray2001
Copy link

cray2001 commented Jun 7, 2023

+1 the problem is not solved

@tony-it-world
Copy link

+1. problem is actual. 2.24.0

florvix7snub added a commit to florvix7snub/allure-plugin that referenced this issue Oct 16, 2023
@florvix7snub
Bugfix for jenkinsci#215
aced246 
Problem caused by DataSetBuilder.build(). The `rowKey` which is an instance of
`TreeSet` is sorted by **natural ordering**.

The values of `rowKey` seems not visible to end users, got a quick way to fix
the issue by adding a prefix to each of them.
@florvix7snub florvix7snub mentioned this issue Oct 16, 2023
Merged
@baev baev closed this as completed in 2156469 Oct 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests