Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
kautkata
@kautkata
@GeorhiiPrystupa it's not supported use one allure step with multiple result dirs
Ezro
@Ezro
Hi everyone. I wasn't able to find any good documentation on this, but is it possible to set allure properties in python without using decorators? (i.e., pytest.allure.severity("Critical") instead @allure.severity("Critical"))
Within the function rather than as a decorator*
Georhii Prystupa
@GeorhiiPrystupa
@kautkata I see. Thank you.
Haytham Elzahar
@haythamelzahar_gitlab
Hi can someone help please - when I generate allure reports using the command line from existing xml reports/data, this produces allure reports with basic features and minimum information. Is there a way to incorporate advanced allure features? Also I am using build.gradle
Eliram Shatz
@eliram
Hi, does anyone knows why allure.description does not work with allure-pytest-bdd - it does work with allure-pytest.
vnpt73
@vnpt73
Hi there, I'm facing with the allure report for multiple browsers. I pass the parameter in XML file to run the test for multiple browsers and I used the allure-cucumber6-jvm for generating the report with the gherkin keywords. but the report only shows the lastest result for only one browser. Any one have solution for this?
vnpt73
@vnpt73
image.png
Hello all, update from me. I already found the solution for this from the historical chat. Thanks for all
dzmitrytesting
@dzmitrytesting
image.png
fescobar
@fescobar

@dzmitrytesting you have to install allure in your jenkins master. Check Configuration> Tools

@KarthikManjrakar the server changed. Use the url https://repo.maven.apache.org/maven2/io/qameta/allure/allure-commandline/2.14.0/allure-commandline-2.14.0.zip

dzmitrytesting
@dzmitrytesting

Hi everyone. Trying to add allure reporter to Jenkins pipeline but faced with the following error (above)
I have added it to global tools installer from maven central (not url, just version from dropdown)
here is mine pipeline:

       stage('Save report') {
            steps {
                stash includes: 'reports/allure-results/**', name: 'reports'
            }
        }
    }
    post {
            always {
                dir('test') {
                    unstash 'reports'
                }

                // sh 'which allure'
                // sh 'npm install -g allure-comandline'
                // sh 'which allure'
                sh 'chmod 777 test/reports/allure-results'

                script {
                    allure results: [[path: 'test/reports/allure-results']]
                }
            }
    }

@fescobar also tried to set up this url in configuration

image.png
fescobar
@fescobar
run in your master allure --version
using console
just to check if it's properly installed
dzmitrytesting
@dzmitrytesting
will try
fescobar
@fescobar
maybe your POSTcode is wrong. Check this one as stage
        stage('Generating Reports'){
            steps {
                allure([
                    includeProperties: false,
                    jdk: '',
                    properties: [],
                    reportBuildPolicy: 'ALWAYS',
                    results: [[path: "test/reports/allure-results"]]
                ])
            }
        }
dzmitrytesting
@dzmitrytesting
allure --version
/var/lib/jenkins/workspace/....@tmp/durable-c5c5e24b/script.sh: 1: /var/lib/jenkins/workspace/....@tmp/durable-c5c5e24b/script.sh: allure: not found

interesting. It's not able.

Just additional thing that agent is:

agent {
        dockerfile {
            args '-u root:root'

        }
    }
fescobar
@fescobar

maybe your POSTcode is wrong. Check this one as stage

        stage('Generating Reports'){
            steps {
                allure([
                    includeProperties: false,
                    jdk: '',
                    properties: [],
                    reportBuildPolicy: 'ALWAYS',
                    results: [[path: "test/reports/allure-results"]]
                ])
            }
        }

try that removing your post block just in case

otherwise try to install again allure
change allure version and when you execute your pipeline check the logs and at the beginning you will see the allure installation (only the first execution after you change the version)
if there is a problem installing that you will see that in the logs
dzmitrytesting
@dzmitrytesting
Interesting. I changed version of allure in tools but job is not trying to install a new one. Will make clear ws and will try it again
fescobar
@fescobar
The installation is not in the job, it's in the master
dzmitrytesting
@dzmitrytesting
oh, you mean agent. Will check logs
fescobar
@fescobar
From my side
  • NODE == AGENT == SLAVE
  • NODE-MASTER == MASTER
the installation is just in the master
dzmitrytesting
@dzmitrytesting
:)
you right :)
dzmitrytesting
@dzmitrytesting
Excuse me for stupid question. additional question. How to find logs in slave? Nothing in default all jenkins log. I created additional logger with jenkins.install but it's not showed.
It's not correct logger?:)
fescobar
@fescobar
check the pipeline, execute that and go to the build number link
in there you will see the console link
dzmitrytesting
@dzmitrytesting
image.png
You mean this one?
Here is nothing regarding installation of new version for reporting
fescobar
@fescobar
check the ending part
when try to read the allure files
if you can not see anything related that it's because your post block is wrong

maybe your POSTcode is wrong. Check this one as stage

        stage('Generating Reports'){
            steps {
                allure([
                    includeProperties: false,
                    jdk: '',
                    properties: [],
                    reportBuildPolicy: 'ALWAYS',
                    results: [[path: "test/reports/allure-results"]]
                ])
            }
        }

try using that please

dzmitrytesting
@dzmitrytesting
I made with your step
fescobar
@fescobar
can you show the logs in that stage?
dzmitrytesting
@dzmitrytesting
yep. 1 min
dzmitrytesting
@dzmitrytesting
[Pipeline] dir
Running in /var/lib/jenkins/workspace/…/test
[Pipeline] {
[Pipeline] unstash
[Pipeline] }
[Pipeline] // dir
[Pipeline] sh
+ chmod 777 test/reports/allure-results
[Pipeline] allure
 docker exec --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** --env ******** bc9430053d95d841aee77da957ad4d5b0b7cf81a82530863383759df2a8df07d /var/lib/jenkins/tools/ru.yandex.qatools.allure.jenkins.tools.AllureCommandlineInstallation/allure/allure-2.14.0/bin/allure generate /var/lib/jenkins/workspace/…/test/reports/allure-results -c -o /var/lib/jenkins/workspace/…./allure-report
OCI runtime exec failed: exec failed: container_linux.go:380: starting container process caused: exec: "/var/lib/jenkins/tools/ru.yandex.qatools.allure.jenkins.tools.AllureCommandlineInstallation/allure/allure-2.14.0/bin/allure": stat /var/lib/jenkins/tools/ru.yandex.qatools.allure.jenkins.tools.AllureCommandlineInstallation/allure/allure-2.14.0/bin/allure: no such file or directory: unknown
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
$ docker stop --time=1 bc9430053d95d841aee77da957ad4d5b0b7cf81a82530863383759df2a8df07d
$ docker rm -f bc9430053d95d841aee77da957ad4d5b0b7cf81a82530863383759df2a8df07d
[Pipeline] // withDockerContainer
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
ru.yandex.qatools.allure.jenkins.exception.AllurePluginException: Can not generate Allure Report, exit code: 126
    at ru.yandex.qatools.allure.jenkins.AllureReportPublisher.generateReport(AllureReportPublisher.java:314)
    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:99)
    at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:69)
    at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
    at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
    at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
    at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
    at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
    at java.base/java.lang.Thread.run(Thread.java:829)
Jenkins not tried to get new version which i put to configuration
image.png
fescobar
@fescobar
but in there you are not trying my configuration

maybe your POSTcode is wrong. Check this one as stage

        stage('Generating Reports'){
            steps {
                allure([
                    includeProperties: false,
                    jdk: '',
                    properties: [],
                    reportBuildPolicy: 'ALWAYS',
                    results: [[path: "test/reports/allure-results"]]
                ])
            }
        }

just add that stage and show me

dzmitrytesting
@dzmitrytesting
image.png
If i will set up it without chmod -> java.nio.file.AccessDeniedException: /var/lib/jenkins/workspace/.../reports/allure-results/testrun.json
fescobar
@fescobar
you have different issues in there
if you are running in docker cotnainer you have to pass the user/group to the container to avoid issues with permissions
dzmitrytesting
@dzmitrytesting
will try to fix it, but it's not a main problem for now :)