kochetkovma/allure-serverSee example on allure.iopump.ru or allure-server.herokuapp.com
shelldocker pull kochetkovma/allure-server:latest docker run -p 8080:8080 kochetkovma/allure-server:latest
Or use docker-compose.yml
docker-compose up -d
Got to http://localhost:8080 - will redirect to OpenAPI (Swagger UI)
To store all data on your local file sytem mount volume:
docker run -p 8080:8080 -v /allure-server-store:/allure kochetkovma/allure-server:latest
Only allure2 supported
Make some allure results and create zip archive with these results, for example allure-results.zip in your root dir
shellcurl --location --request POST 'http://localhost:8080/api/result' \ --form 'allureResults=@/allure-results.zip;type=application/zip'
Response:
{ "fileName": "allure-results.zip", "uuid": "1037f8be-68fb-4756-98b6-779637aa4670" }
Save uuid
Don't forget specify form item Content type as application/zip. Server works with zip archives only!
For generate new report execute POST request with json body:
shellcurl --location --request POST 'http://localhost:8080/api/report' \ --header 'Content-Type: application/json' \ --data-raw '{ "reportSpec": { "path": [ "master", "666" ], "executorInfo": { "buildName": "#666" } }, "results": [ "1037f8be-68fb-4756-98b6-779637aa4670" ], "deleteResults": false }'
Response:
{ "path": "master/666", "url": "http://localhost:8080/allure/reports/master/666/index.html" }
Memorize url
WARNING: Generated Reports, and their History are grouping by
pathkey. This key means something likeprojectorjoborbranch. The latest report with the samepathwill be active: It is not a real path - it's a logical path. The same situation withpathcolumn in GUI!
After generating you can access the report byhttp://localhost:8080/allure/reports/master/666/index.html
You may get all reports
shellcurl --location --request GET 'http://localhost:8080/api/report'
Or by path as branch name master
shellcurl --location --request GET 'http://localhost:8080/api/report?path=master'
You may get all uploaded results:
shellcurl --location --request GET 'http://localhost:8080/api/result'
Clear results or reports:
shellcurl --location --request DELETE 'http://localhost:8080/api/result' curl --location --request DELETE 'http://localhost:8080/api/report'
Allure Server provide WEB UI to access to reports and results.
By default WEB UI is available on path /ui and there is redirection from / to /ui
Example: http://localhost:8080/ui
WEB UI provides the same functions as a REST API
WEB UI is implemented with Vaadin 14
WARNING: Generated Reports, and their History are grouping by
pathkey. This key means something likeprojectorjoborbranch. The latest report with the samepathwill be active: It is not a real path - it's a logical path. The same situation withpathcolumn in GUI!
Main Page Main Page
See example on allure.iopump.ru or allure-server.herokuapp.com
[***]

探索更多轩辕镜像的使用方法,找到最适合您系统的配置方式
通过 Docker 登录认证访问私有仓库
在 Linux 系统配置镜像服务
在 Docker Desktop 配置镜像
Docker Compose 项目配置
Kubernetes 集群配置 Containerd
K3s 轻量级 Kubernetes 镜像加速
VS Code Dev Containers 配置
MacOS OrbStack 容器配置
在宝塔面板一键配置镜像
Synology 群晖 NAS 配置
飞牛 fnOS 系统配置镜像
极空间 NAS 系统配置服务
爱快 iKuai 路由系统配置
绿联 NAS 系统配置镜像
QNAP 威联通 NAS 配置
Podman 容器引擎配置
HPC 科学计算容器配置
ghcr、Quay、nvcr 等镜像仓库
无需登录使用专属域名
需要其他帮助?请查看我们的 常见问题Docker 镜像访问常见问题解答 或 提交工单
免费版仅支持 Docker Hub 访问,不承诺可用性和速度;专业版支持更多镜像源,保证可用性和稳定速度,提供优先客服响应。
专业版支持 docker.io、gcr.io、ghcr.io、registry.k8s.io、nvcr.io、quay.io、mcr.microsoft.com、docker.elastic.co 等;免费版仅支持 docker.io。
当返回 402 Payment Required 错误时,表示流量已耗尽,需要充值流量包以恢复服务。
通常由 Docker 版本过低导致,需要升级到 20.x 或更高版本以支持 V2 协议。
先检查 Docker 版本,版本过低则升级;版本正常则验证镜像信息是否正确。
使用 docker tag 命令为镜像打上新标签,去掉域名前缀,使镜像名称更简洁。
来自真实用户的反馈,见证轩辕镜像的优质服务