Skip to content
Advertisement

Error integration Allure reporting with Jenkins. Can’t find allure commandline

Please help, I just have no clue what is going wrong, I’ve tried everything… This is a QA test project, based on java17, maven, testng. Integrеtion between Jenkins and Allure doesn’t work, what is going wrong?

I have post condition in Jenkins file :

JavaScript

And when I’m running pipeline on Jenkins side, I get below error in console output

Pipeline allure Error when executing always post condition: Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to ubuntu-20.04 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1797) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356) at hudson.remoting.Channel.call(Channel.java:1001) at ru.yandex.qatools.allure.jenkins.tools.AllureCommandlineInstallation.getMajorVersion(AllureCommandlineInstallation.java:63) at ru.yandex.qatools.allure.jenkins.ReportBuilder.build(ReportBuilder.java:52) at ru.yandex.qatools.allure.jenkins.AllureReportPublisher.generateReport(AllureReportPublisher.java:312) at ru.yandex.qatools.allure.jenkins.AllureReportPublisher.perform(AllureReportPublisher.java:231) at jenkins.tasks.SimpleBuildStep.perform(SimpleBuildStep.java:123) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:100) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:70) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) java.io.IOException: Can’t find allure commandline at ru.yandex.qatools.allure.jenkins.tools.AllureCommandlineInstallation$GetMajorVersion.call(AllureCommandlineInstallation.java:74) at ru.yandex.qatools.allure.jenkins.tools.AllureCommandlineInstallation$GetMajorVersion.call(AllureCommandlineInstallation.java:65) at hudson.remoting.UserRequest.perform(UserRequest.java:211) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:376) at hudson.remoting.InterceptingExecutorService.lambda$wrap$0(InterceptingExecutorService.java:78) at java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) at java.lang.Thread.run(Thread.java:833)

Integration with Allure installed correctly on Jenkins side ( I’ve tried to remove “/bin” path from HOME directory in Jenkins Agent config, but it didn’t helped. Project use java17, maven.

JavaScript
JavaScript

Advertisement

Answer

Allure jenkins install config

I found the answer by myself, this is some kind of issue in fresh versions of allure-commandline, try to :

  1. install old version, for instance 2.8.0
  2. then you could install any new version

Seems like in old version, while installation, it’s creating path(for ubuntu in my case) in correct direction, and then just update with a new one… Or you can insert installation directory manually and initially install a new version

User contributions licensed under: CC BY-SA
1 People found this is helpful
Advertisement