Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
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 :)
fescobar
@fescobar
everything is related.
I imagine you are mounting a volume and in there you are generating the results files
or not?
dzmitrytesting
@dzmitrytesting
I didn't use volume in agent configuration
        dockerfile {
            args '-u root:root'
        }
fescobar
@fescobar
can you see those allure results files in your workspace after executing the pipeline/
?
dzmitrytesting
@dzmitrytesting
yeah

Sorry mate, unfortunately for me i need to go.

Many-many-many thanks for you helping. I will check permissions too when i will back to home

fescobar
@fescobar
ok
Deepika-QA
@Deepika-QA
Hi guys would you recommend using allure reports for a nunit framework that uses specflow , selenium and c# and Azure Devops. Has any one used it in a similar setup?
Vamsi Verma
@vamsi190294
image.png
Hi Guys, i'm trying to use the history feature to check previous test runs. But, i am not able to click on any past runs to see more details about the run like it does in retries.
how do i fix this? i want to compare the run time with previous runs of the test
anaskhan89
@anaskhan89:matrix.org
[m]

Hi Guys, I am configuring allure reports in my existing automation framework that consist of Java, maven, cucumber and junit.
I've configured it rightly by following allure documentation (https://docs.qameta.io/allure/#_cucumber_jvm). But when i am running mvn test , it gives following exception:
The forked VM terminated without saying properly goodbye. VM crash or System.exit called...
It is not able to load "-Dcucumber.options=--plugin ru.yandex.qatools.allure.cucumberjvm.AllureReporter"
Can someone please help me?

PS: It generates the report when i am running tests from feature files, but i need to run it through maven because i have to integrate these results in jenkins pipeline

Kaushik6Test
@Kaushik6Test
Hello guys, I ain't sure whether this is right place to post this question
zaqqaz/jest-allure#78
I have been facing issue while using jest allure for generating reports. Everything seems to be fine until I open index.html file and find it blank. I have mentioned the ticket above where you might find the details.
anaskhan89
@anaskhan89:matrix.org
[m]

:point_up: Edit: Hi Guys, I am configuring allure reports in my existing automation framework that consist of Java, maven, cucumber and junit.
I've configured it rightly by following allure documentation (https://docs.qameta.io/allure/#_cucumber_jvm). But when i am running mvn test , it gives following exception:
The forked VM terminated without saying properly goodbye. VM crash or System.exit called...
It is not able to load "-Dcucumber.options="--plugin io.qameta.allure.cucumber4jvm.AllureCucumber4Jvm"
Can someone please help me?

PS: It generates the report when i am running tests from feature files, but i need to run it through maven because i have to integrate these results in jenkins pipeline

Roy de Kleijn
@roydekleijn