jenkinsci / allure-plugin

Allure Jenkins Plugin
https://plugins.jenkins.io/allure-jenkins-plugin/
Other
85 stars 67 forks source link

Unable to generate Allure Report from Jenkins even though successfully generated message #185

Closed aeroclee closed 6 years ago

aeroclee commented 6 years ago

Issue

Hello, I am able to see one instance of allure report when I execute from the command-line (allure serve target\allure-results) after build success. However, I am not able to see allure report from the Jenkins. I see the successfully generated report correctly, but no report data in the User interface.

Not sure what is wrong with this.

Reference: image

POM:

2.0-BETA21 io.qameta.allure allure-testng ${allure-adaptor.version} test io.qameta.allure allure-java-commons ${allure-adaptor.version} io.qameta.allure allure-maven 2.9 **Commandline: After Build Success,** type from the Commandline: allure serve target\allure-results Generating report to temp directory... Report successfully generated to C:\Users\username\AppData\Local\Temp\1783018463190181457\allure-report Starting web server... 2017-12-07 11:42:25.795:INFO::main: Logging initialized @2012ms to org.eclipse.jetty.util.log.StdErrLog Server started at http://172.16.42.53:58150/. Press to exit **Jenkins: After Build Success,** $ "C:\Program Files (x86)\Jenkins\tools\ru.yandex.qatools.allure.jenkins.tools.AllureCommandlineInstallation\Allure_Report\bin\allure.bat" generate "C:\Program Files (x86)\Jenkins\workspace\DV\target\allure-results" -c -o "C:\Program Files (x86)\Jenkins\workspace\DV\allure-report" Report successfully generated to C:\Program Files (x86)\Jenkins\workspace\DV\allure-report Allure report was successfully generated. Creating artifact for the build. Artifact was added to the build. Finished: SUCCESS ![image](https://user-images.githubusercontent.com/32941858/33743717-d6568058-db62-11e7-9213-b8f3a09ccd68.png) ![image](https://user-images.githubusercontent.com/32941858/33743727-e55bbdac-db62-11e7-8eab-a2a0ec84483d.png) Allure Global Configuration: Download URL for binary https://bintray.com/qameta/generic/download_file?file_path=io%2Fqameta%2Fallure%2Fallure%2F2.4.1%2Fallure-2.4.1.zip ![image](https://user-images.githubusercontent.com/32941858/33743760-fc952986-db62-11e7-8286-7d398bf7886d.png) ![image](https://user-images.githubusercontent.com/32941858/33743773-0995382e-db63-11e7-8339-69e204768436.png) Maven POM File: Maven: pom.xml file 4.0.0 com.boeing.vancouver DVWindow 0.0.1-SNAPSHOT DVAT Test DV Surface Windows Version Test UTF-8 3.6 2.0-BETA21 ${project.build.directory}/allure-results 5.0.4 1.8.13 23.0 4.5 2.0 2.20.1 42.1.4 3.6.0 4.5.1 1.7.25 4.3.10.RELEASE 6.11 org.testng testng ${testng.version} org.hamcrest hamcrest-all 1.3 test org.slf4j slf4j-simple 1.7.21 test org.apache.commons commons-lang3 ${apache.commons.version} io.qameta.allure allure-testng ${allure-adaptor.version} test io.qameta.allure allure-java-commons ${allure-adaptor.version} io.appium java-client ${appium.version} org.seleniumhq.selenium selenium-java ${selenium.version} com.codeborne selenide ${selenide.version} com.google.guava guava ${guava.version} org.apache.httpcomponents httpclient ${httpclient.version} org.uncommons reportng 1.1.4 test org.apache.logging.log4j log4j-api 2.8.2 org.apache.logging.log4j log4j-core 2.8.2 org.springframework spring-context ${springframework.version} org.springframework spring-core ${springframework.version} org.springframework spring-jdbc ${springframework.version} org.springframework spring-expression ${springframework.version} org.springframework spring 2.5.6 org.postgresql postgresql ${postgresql.version} org.slf4j slf4j-api ${slf4j.version} com.linuxense javadbf 0.4.0 net.sourceforge.javacsv javacsv ${javacsv.version} central libs-release https://pdmaven.devprojecteagle.com/artifactory/libs-release false snapshots libs-snapshot https://pdmaven.devprojecteagle.com/artifactory/libs-snapshot false AllTestSuites true org.apache.maven.plugins maven-surefire-plugin ${maven-surefire-plugin.version} TestSuite.xml methods 5 ${project.basedir}/resources usedefaultlisteners false allure.results.directory ${allure.results.directory} target/ org.apache.maven.plugins maven-resources-plugin 3.0.2 copy-allure-environment validate copy-resources ${allure.results.directory} src/main/resources org.apache.maven.plugins maven-compiler-plugin 3.5 1.8 1.8 org.apache.maven.plugins maven-surefire-plugin {maven-surefire-plugin.version} false -javaagent:${settings.localRepository}/org/aspectj/aspectjweaver/${aspectj.version}/aspectjweaver-${aspectj.version}.jar org.aspectj aspectjweaver ${aspectj.version} true io.qameta.allure allure-maven 2.9 allure-report
aeroclee commented 6 years ago

Sorry. looks like this is not the issues with the plugs in. I referenced workspace in my local development folder instead of Jenkins workspace.

After copied my local development workspace location (C:\Users\user\workspace\DV) to Jenkins workspace location (C:\Program Files (x86)\Jenkins\workspace\DV) and build Jenkins Job, I was able to see the allure report correctly.

Thanks