allure-framework / allure-framework/allure2

Allure plugin for Gitlab CI/CD

Open
#891 18 comments 88 reactions 0 assignees View on GitHub
Dominant language
HTML
Stars
5.5k
Forks
782
Avg merge
2d 33m
Merged PRs (30d)
16

Description

**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.

Contributor guide

Open the contributing guide

Research direction

No repository file or test is named in the issue. Start with the GitLab CI/CD .yml snippet and the Jenkins integration referenced in the request, then determine how Allure reports and execution trends could be rendered inside GitLab; done means a working GitLab plugin that avoids downloading reports or serving them separately.

Written by the indexing model from the issue text.

Assessment

Tech stack
gitlab, java
Domain
ci-cd, testing
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.