Allure trend not shown for Pipeline job on Jenkins

andrcuns commented 7 years ago

Issue

When reports are generated in jenkins Freestyle jobs, allure plugin adds test result trend on the jobs front page. This doesn't happen if it is a Pipeline job.

Context

Jenkins version: 2.66
Job type: Pipeline
Allure plugin version: 2.23
Allure commandline version: 2.4.1

Problem description

Describe your problem in a meaningful way:

what were you doing Running pipeline job that generates allure report in the end from Jenkinsfile.
what was expected Job front view should contain test result trend.
what occurred finally Pipeline job doesn't contain test result trend like Freestyle job does.

Logs & Traces

Please include any relevant log that could serve to better understand the source of your issue Freestyle job screenshot:

Pipeline job screenshot: screen shot 2017-10-26 at 16 57 05

roman-ponomarenko commented 6 years ago

@baev is this bug going to be fixed?

goncharenkov commented 6 years ago

is there any workaround for this issue ?

germandavid85 commented 6 years ago

+1

azakordonets commented 6 years ago

+1

giedriusramas commented 6 years ago

is still does not work

giedriusramas commented 6 years ago

I cannot see allure-history trend on pipeline jobs. I have installed 2.26.0 plugin version.

shadow1163 commented 6 years ago

try this line "allure report: 'allure_reports', results: [[path: 'allure_results']]"

Smalkoy commented 5 years ago

Trends are not displayed because the job is failing all the time. As soon as it will be executed with success status the trends graph will appear with info about all previous builds.

sachindast commented 4 years ago

Hello Team,

Reporting the issue again on Auget 2020

Issue still seeing in Jenkins - log says Allure report was successfully generated but empty coming, same is working with normal Jenkins job that uses post-build section to perform allure reports.

Jenkins version : 2.209 allure plugin version : 2.28.1

below is a snippet of the problem

Report successfully generated to /home/allure_pipeline/allure-report Allure report was successfully generated. Creating artifact for the build. Artifact was added to the build.

i'm using within post build section as below :

always { node('build-machine') { sh 'mkdir -p $WORKSPACE/{allure-report,reports}' allure includeProperties: false, jdk: '', results: [[path: 'reports/']] } }

even I have tried by putting it as a stage.

tage('reports') { steps { script { allure([ includeProperties: false, jdk: '', properties: [], reportBuildPolicy: 'ALWAYS', results: [[path: 'reports/']] ]) } } }

I have tried most of the possible ways, let me know if there are any problems the way I'm doing?

Thanks in advance, Sachin Das jenkins_allure_report

alexKazarin commented 2 years ago

@giedriusramas I came up to one more 'workaround'. (hope that could help somebody) To make Allure Trend and Allure report menu item on left panel to be presented, even when no green/pass builds exists: Failed builds in fact must be in status Unstable (this is due to misinterpretation of statuses by allure-report and jenkins)

To achieve this, you could add to your groovy script: if (currentBuild.currentResult == 'FAILURE') { currentBuild.rawBuild.@result = hudson.model.Result.UNSTABLE }``

jenkinsci / allure-plugin