aleksandr-kotlyar / gitlab-allure-history Goto Github PK

https://gitlab.com/aleksandr-kotlyar/gitlab-allure-history

What?

1. create empty branch and push allure-report there by job_number
2. create history trends by copying history.json and creating executor.json for linked trends

Why?

For the next step of publishing tree with allure-reports on gitlab-pages

What happened?

When you delete branch from repository - it's page on GitLab Pages become unavailable - redirects you to 404 when you try to open branch from tree, or when you move to it's jobs runs through the cached/saved URL. Example:

Cause?

GitLab Pages are publishing from the same branch the pipeline execution was. And when you delete branch from repo - GitLab Pages removes all links to it's job artifacts, even if job and it's artifacts are still exist. Seems it's a GitLab feature.

What to do?

Make GitLab Pages insensitive to branch deletions. It can be done by creating separate pipeline which publishes GitLab Pages only from the branch which stores all allure report history.

Plan

• execute pages job only on 'gl-pages' branch.
• trigger pipeline with 'gl-pages' branch from every 'allure' job.
• lock execution of any other jobs on 'gl-pages' branch except 'pages' job.

What?

Add first tests on python as example with simulation of next results:

1. pass
2. fail
3. broken
4. skipped

Why?

To demonstrate in allure reports later.

What?

Add job with allure report generation and store generatedd allure-report as artifact

Why?

To make the next step with collecting allure-reports possible.

What?

Publish allure-reports on gitlab pages with navigation between them.

Why?

To have allure reports and their history trends on the host.

Create Dockerfile with fixed versions

• alpine13
• python3.7.9
• openjdk8-jre

Hello, can you help me provide scrpit yml allure history for cypress ?
please help me sir

Now it looks like:

After adding column with date modified it should look like:

create a job with allure-results artifacts