Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
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
@vamsi-verma-s
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
Anyone? allure-framework/allure-maven#183
fescobar
@fescobar
@roydekleijn https://stackoverflow.com/a/50499775/10299604
Pyae Phyo
@NickPyae
hello, can anyone plz share me how I can generate pytest junitxml report using allure-pytest? so far what I have seen is I can generate only json reports using allure. This is the command I'm using right now -> pytest --alluredir=./allure test/
fescobar
@fescobar
@NickPyae allure json/xml results files is not related with junitxml . They are both different formats
Pyae Phyo
@NickPyae
With pytest, we can generate junitxml file with this command -> pytest /test --junitxml=/report.xml. So I'm looking for something like this with allure-pytest too. Is there anyway we can do this in allure-pytest @fescobar .
fescobar
@fescobar
@NickPyae allure 1 generates xml file, allure2 generates json files. That is the commandpytest tests/*.py --alluredir=allure-results
here an example (skip docker part) https://github.com/fescobar/allure-docker-service-examples/tree/master/allure-docker-python-pytest-example
Pyae Phyo
@NickPyae
thx u @fescobar I will give this a try
tiagon97
@tiagon97
Hello guys, maybe someone can help me, im new to Jenkins trying to configure pipeline for cypress automation tests, i receive below error:
The input line is too long.
The syntax of the command is incorrect.
FATAL: Can not generate Allure Report, exit code: 255
I've already seen jenkinsci/allure-plugin#199 this post but workarounds mentioned here do not work for me.
stage('Report') { steps { script { allure([ includeProperties: false, jdk: '', properties: [], reportBuildPolicy: 'ALWAYS', results: [[path: 'allure-results']] ]) } } }
Sam Lewis
@sam1ewis_twitter
Hey guys, is there any way that I can serve a generated report to the host machine from inside a docker container? I have Allure generating reports inside the docker container, and the allure command is working. However, when trying to access the URL from outside the container, it times out. I've tried '-network=host' and opening ports etc but still can't access the report. Thanks!
fescobar
@fescobar
@sam1ewis_twitter https://github.com/fescobar/allure-docker-service
Sam Lewis
@sam1ewis_twitter
Thanks @fescobar , that would typically be a great solution. In my case I want to only use a single container. This container is running our pytest tests and then generating the report based on the results on the container. I was hoping there was a way I could access the web server from the host machine
fescobar
@fescobar
@sam1ewis_twitter just you need to attach the volume where the report was generated.
Sam Lewis
@sam1ewis_twitter
@fescobar I wanted to not have the dependance of installing Allure on the host machine.. I have solved it by exposing the ports of the container and then using --port <port_number> and --host 0.0.0.0 in the allure serve command from inside the container. Now I can access the report with all dependancies in the container. Thanks for your help! :)
manukgr
@manukgr
image.png