Migrate allure to new CI component
What does this MR do?
Migrate allure to new allure CI component
The old allure template has been removed in gitlab-org/quality/pipeline-common!439 (merged), causing pipeline failures on all branches.
- This needs to be backported to stable branches.
- This does not affect the
dev.gitlab.org
fork.
Related issues
Author checklist
For general guidance, please follow our Contributing guide.
Required
For anything in this list which will not be completed, please provide a reason in the MR discussion.
-
Merge Request Title and Description are up to date, accurate, and descriptive. -
MR targeting the appropriate branch. -
MR has a green pipeline. -
Documentation created/updated. -
Tests added/updated, and test plan for scenarios not covered by automated tests. -
Equivalent MR/issue for omnibus-gitlab opened.
Reviewers checklist
-
MR has a green pipeline on https://gitlab.com/gitlab-org/charts/gitlab. -
Consider downstream impact to the Operator, as per evaluating impact from changes to GitLab Chart.
Edited by Clemens Beck