On Jenkins Pipeline, Reports are not being generated correctly

[ch-akash]

Hi All,

I was trying to integrate Allure with our Jenkins pipeline. After the execution of tests, I can see this message on Jenkins console:

Jenkins Logs

---

17:06:52 [PAM_tests_PR-131] $ /cara-jenkins-workspace/tools/ru.yandex.qatools.allure.jenkins.tools.AllureCommandlineInstallation/allure/bin/allure generate -c -o /cara-jenkins-workspace/workspace/PAM_tests_PR-131/allure-report

17:06:53 allure-results does not exist

17:06:54 Report successfully generated to /cara-jenkins-workspace/workspace/PAM_tests_PR-1[3](https://supermarket-jenkins.test.h.zeal.zone/job/PAM/job/tests/job/PR-131/2/pipeline-console/?start-byte=0&selected-node=407#log-3)1/allure-report 17:06:54 Allure report was successfully generated.

But when we try to open Allure report, it looks broken.

Jenkins File:

---

 post {
                                always {
                                    script {
                                        allure([
                                                includeProperties: false,
                                                reportBuildPolicy: 'ALWAYS',
                                                results          : [[path: 'allure-results']]
                                        ])

We Tried To Replicate On Local Machine

---

Initially, I thought the location of allure-results on Jenkins is not correct in out Jenkinsfile but whenI tried the generate command to replicate issue on local and here is what I found:

1. ✅ Allure serve worked on local and I can see a valid report
2. allure-results folder exists and I can see the data in it:

3. ❌ When I used Allure generate (allure generate -c -o allure-results) command with allure-results folder, it gave me same error message that
4. Console message from step 3

allure-results does not exist
Report successfully generated to allure-results

5. This is what allure-results folder becomes after allure generate command

6. If I open the report from step 3 with allure open command, it is same as on Jenkins(with broken data as below)

Project Dependencies

---

testImplementation("io.qameta.allure:allure-junit-platform")
testImplementation("io.qameta.allure:allure-cucumber7-jvm")
implementation group: 'io.qameta.allure', name: 'allure-rest-assured', version: '2.28.1'

I saw a similar question #2585 but it does not look the same issue in my case.

Any help or suggestions will definitely help me. This is my first time I am having any issues with Allure and most of the time the documentation is always enough. Not sure what is wrong in this setup.