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
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
Hi friends, allure with report is generating other files but not results.json. Need help
fescobar
@fescobar
@manukgr what library are you using?
manukgr
@manukgr
allure-pytest
fescobar
@fescobar
@manukgr check this example to generate results properly https://github.com/fescobar/allure-docker-service-examples/tree/master/allure-docker-python-pytest-example (ignore the docker part)
manukgr
@manukgr
@fescobar its working in my demo setup, but in actual setup there is some issue, only result files are not generated, container and attachment are generated, do you know any way to log allure-pytest in DEBUG mode or verbose
fescobar
@fescobar
@manukgr I don't know what setup you are using, just I'm giving you an example to compare and check what you are doing wrong.
manukgr
@manukgr
alright @fescobar Thanks
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']] ]) } } }
kot99a
@kot99a
Hello everyone, I'm trying to add an image to the report via AllureReporter. addAttachment(). I have visual tests. Using wdio/image-comparison, I check the forms. I have a folder with the expected results. I want to add the expected screenshot to the report, which is stored in the folder. I want to do it through AllureReporter.addAttachment(). But for some unknown reasons, I can't attach the path to the file. Maybe someone has encountered this and can give some example of how to attach a picture from a folder to a report. I will be grateful for your help
1 reply
SimoneB
@borecz
hello, anyone using allure with playwright here?
daraghcurtis
@daraghcurtis
Hi All . Does anyone have a good WORKING jbehave-allure template for Java. I have tried installing from this , but I cant get it working , even though I am installing via Gradle (https://github.com/allure-framework/allure-java) Any suggestions would be greatly appreciated
Deepika-QA
@Deepika-QA
has anyone used specflow living document
dschaitu322
@dschaitu322
Hello Everyone,
can someone help me building Jenkins dsl publisher step for allure
publishers {
allure(['allure-results'])
}
fescobar
@fescobar
@dschaitu322 for pipeline or job?
dschaitu322
@dschaitu322
above code not working with Jenkins DSL and everytime I need to add Postbuild action manually
I'm using DSL jobs
pipeline script is working fine with Jenkins file
fescobar
@fescobar

publishers {
allure(['allure-results'])
}

that code is fine, works for me

what is the error?
@dschaitu322
dschaitu322
@dschaitu322
No error observed, Allure not reflecting in Post build action
fescobar
@fescobar
check the logs if it's executing that
if you see in the logs to allure trying to collect results, it's because you are not using the right path
dschaitu322
@dschaitu322
when some code pushed to jenkins job dsl allure is getting removed, again user has to configure manually in post build action step
Allure configuration not taking from publisher
fescobar
@fescobar
@dschaitu322 that is something wrong with your configuration
you need to check what branch is taking when generates the dsl
dschaitu322
@dschaitu322
I tried something like this which is not helping
project / publishers << 'ru.yandex.qatools.allure.jenkins.AllureReportPublisher' {
includeProperties false
reportBuildPolicy 'ALWAYS'
results {
path 'automationReports/allure-results'
}
}
fescobar
@fescobar

No, it's fine how are you using the snippet here

publishers {
allure(['allure-results'])
}

it works perfect for me, you have another config wrong
the problem is when you re run the dsl generator again
also, check if you snippet is in the same level that steps{} (not inside)
dschaitu322
@dschaitu322
in my case I cannot see allure reflecting in POST build actions
fescobar
@fescobar
if you can share the complete dsl would be better, otherwise i cant help you
dschaitu322
@dschaitu322
remaining things like publishHtml, extendedEmail in publishers are reflecting immediately when configured in dsl
publishers {
extendedEmail {
recipientList('$DEFAULT_RECIPIENTS')
defaultSubject('$DEFAULT_SUBJECT')
        contentType('text/html')

        triggers {
            always {
                subject('$PROJECT_DEFAULT_SUBJECT')
                content('$DEFAULT_CONTENT')
                sendTo{
                    recipientList()
                }
             }
          }
       }
        archiveArtifacts {
            pattern('automationReports/**/*')
            pattern('${LOGGING_DIR}/*')
            fingerprint()
            allowEmpty()
        }
        publishHtml {
            report('allure-report') {
                reportName('Test Output')
            }
            report('test') {
                reportName('Allure Tests')
                keepAll()
                allowMissing()
                alwaysLinkToLastBuild()
            }
       }
        allure(['automationReports/allure-results/'])
fescobar
@fescobar
can you include the proper closed brackets
test your script just adding the allure result section
maybe is conflicting with another plugin/config
just create a simple dsl and check if the problem persist
on that way you can provide me a specific example and I can reproduce that in my env
dschaitu322
@dschaitu322
publishers {
extendedEmail {
recipientList('$DEFAULT_RECIPIENTS')
defaultSubject('$DEFAULT_SUBJECT')
        contentType('text/html')

        triggers {
            always {
                subject('$PROJECT_DEFAULT_SUBJECT')
                content('$DEFAULT_CONTENT')
                sendTo{
                    recipientList()
                }
             }
          }
       }
        archiveArtifacts {
            pattern('automationReports/**/*')
            pattern('${LOGGING_DIR}/*')
            fingerprint()
            allowEmpty()
        }
        publishHtml {
            report('allure-report') {
                reportName('Test Output')
            }
            report('test') {
                reportName('Allure Tests')
                keepAll()
                allowMissing()
                alwaysLinkToLastBuild()
            }
       }
       allure(['automationReports/allure-results/'])
    }