Allure plugin for Gitlab CI/CD

allure-framework / allure2

Allure Report is a flexible, lightweight multi-language test reporting tool. It provides clear graphical reports and allows everyone involved in the development process to extract the maximum of information from the everyday testing process

https://allurereport.org/

Apache License 2.0

4.26k stars 717 forks source link

Allure plugin for Gitlab CI/CD #891

Open microlia opened 5 years ago

microlia commented 5 years ago

Is your feature request related to a problem? Please describe. We use Gitlab CI/CD for running autotests (Java + TestNG + Selenide) as we have requirements for this. But in gitlab the only thing I was able to do is to create inside docker image allure report and attach it to job run as zip archive. Then you should download it and open locally. Using allure in such way doesn't allow us to have execution trend at all as far as we have to do some magic with all browsers to see it with its jsons. I was searching an option to do it in gitlab itself (for example using their html view) and there is no option also.

this is part of my *.yml file. `after_script:

cd qa-tests
mvn allure:report artifacts: when: always name: "Report" paths:
- $CI_PROJECT_DIR/qa-tests/target/site/allure-maven-plugin/ expire_in: 15 days`

Describe the solution you'd like to create a plugin for gitlab as for Jenkins to have all allure features and the option to see reports inside gitlab without downloading reports and serving them on separate server.

psyreactor commented 5 years ago

just-boris commented 5 years ago

As far as I can tell, gitlab ci does not provide an extension point to build custom build reports: https://gitlab.com/gitlab-org/gitlab-ce/issues/33943

Therefore it is not possible to build a jenkins-style plugin there. I guess this issue need to be filed to the Gitlab organization first, asking for such an extension point.

Zeff commented 5 years ago

@microlia we already have issues and roadmap items related to test reporting that are slated for Q4 this year, but we're working on an internal solution for the quality engineering team (of which I'm a member). I'm personally starting to work on this within the next week.

Have you considered trying to deploy your generated reports to GitLab Pages so you don't have to download the artifacts? I'm not familiar with Allure yet, which will shortly change, but I would imagine you would be able to do something like we did with our coverage reports. See this blog post here:

https://about.gitlab.com/2016/11/03/publish-code-coverage-report-with-gitlab-pages/

In the meantime, I will try to post back here when I make some progress and I think I will need to publish a new blog post specific to integrating Allure. When I get an issue/merge request opened up, I'll reference it here so you can interact with us directly. 👍

And thanks to the Allure folks for publishing such a great tool!

baev commented 5 years ago

@Zeff do you mind to have a more deep integration with Allure? It would be so awesome, I can share our project vision and what integrations we can done.

Zeff commented 5 years ago

@baev I would imagine we'll eventually want something like that. This phase is more of an internal workaround until we decide on how to approach a solution for reporting and it's also an investigation into how Allure might fit those needs. I'm a bit transient through next week, but let's chat sometime after 5/14. What's the best way to reach out to you?

baev commented 5 years ago

but let's chat sometime after 5/14

:+1:

What's the best way to reach out to you?

You can use Gitter or mail to allure at qameta.io

IbbuGit commented 5 years ago

Hi Any updates on this. Allure plugin is very much needed for our project. kindly help on this.

kochetkov-ma commented 4 years ago

look at https://github.com/kochetkov-ma/allure-server and image https://hub.docker.com/r/kochetkovma/allure-server

yaboeing commented 4 years ago

If your gitlab has enabled pages feature and your group is public( or private by commit below), you will see the index.html allure report page in a separate tab as static site. It woks for our on-premse gitlab. ref https://docs.gitlab.com/ee/ci/pipelines/job_artifacts.html As I understood a bit fixed by commit https://gitlab.com/gitlab-org/gitlab/-/commit/d1bfec9ba9852ccd677e9e2b53b91536c61114a9