DEV.co
Open-Source Testing · fescobar

allure-docker-service

Allure Docker Service is a containerized solution that automatically generates and serves test reports from Allure Framework results. It monitors a mounted directory for test result changes and regenerates reports in real-time without manual intervention.

Source: GitHub — github.com/fescobar/allure-docker-service
741
GitHub stars
206
Forks
Python
Primary language
Apache-2.0
License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

FieldValue
Repositoryfescobar/allure-docker-service
Ownerfescobar
Primary languagePython
LicenseApache-2.0 — OSI-approved
Stars741
Forks206
Open issues43
Latest releasev2.38.1 (2026-03-23)
Last updated2026-03-23
Sourcehttps://github.com/fescobar/allure-docker-service

What allure-docker-service is

Docker-based service wrapping Allure 2 that provides file-system watching, automatic report generation, and a web UI. Supports single/multi-project setups, API-driven result submission, TLS, authentication, and Kubernetes deployment via manifest lists across amd64, arm32v7, and arm64v8 architectures.

Quickstart

Get the allure-docker-service source

Clone the repository and explore it locally.

terminalbash
git clone https://github.com/fescobar/allure-docker-service.gitcd allure-docker-service# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Local development test reporting

Developers running regression tests locally can see live-updating Allure reports by mounting their allure-results directory, eliminating manual report generation steps.

Multi-project team dashboards

QA teams can aggregate test results from multiple projects into a single Allure instance, providing centralized visibility into test status across the organization.

CI/CD pipeline reporting

Integration with Jenkins, GitHub Actions, or container orchestration (Kubernetes) for automated report generation and archival alongside test execution.

Implementation considerations

  • Requires test automation framework integration (Java TestNG/JUnit4, Node.js Cucumber, Python pytest/Behave, C# SpecFlow, etc.) to generate Allure-compatible results before the service can report on them.
  • File-system polling interval is configurable but introduces latency between result generation and report availability; API submission offers more deterministic triggering.
  • Storage optimization and history/trend retention must be explicitly configured; default behavior may accumulate large result sets over time.
  • Multi-instance setups and custom URL prefixes require careful configuration in container orchestration environments to avoid port conflicts and routing issues.
  • Authentication and TLS support exist but require credentials management and certificate provisioning; not enabled by default.

When to avoid it — and what to weigh

  • Strict test result isolation required — If security or data segregation mandates complete isolation between projects or tenants, the multi-project architecture may require additional controls.
  • Real-time analytics at massive scale — Allure Docker Service is file-system-driven and may not scale efficiently for thousands of concurrent projects or high-frequency result submissions without custom optimization.
  • Custom report formats without templating — While emailable report customization is supported, significant deviations from Allure's standard report structure require direct plugin development or template overrides.
  • Zero external dependency environments — The service requires Docker, Java (11+ via eclipse-temurin base image), and network access for pulling base images; air-gapped deployments need pre-built container images.

License & commercial use

Apache License 2.0 (Apache-2.0). Permissive OSI-approved license permitting commercial use, modification, and distribution under the same license terms with liability disclaimers.

Apache-2.0 explicitly permits commercial use, modification, and redistribution provided that the license and notice files are included in distributed works. No commercial support, SLA, or warranty is provided by the project; commercial users should review the LICENSE file and consider support options through community channels or forks.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

SignalAssessment
MaintenanceActive
DocumentationAdequate
License clarityClear
Deployment complexityModerate
DEV.co fitGood
Assessment confidenceHigh
Security considerations

Default deployment exposes the web UI and API without authentication. Security features (login, X-CSRF-TOKEN, role-based access, public endpoint toggles) must be explicitly enabled and configured. No mention of input validation, SQL injection, or dependency vulnerability scanning in provided data. TLS support is available but requires certificate provisioning. API endpoints accept file uploads (multipart/form-data) without clear rate-limiting or file-size constraints documented. Base images (eclipse-temurin:11-jre) should be monitored for CVE updates; no security advisory process is documented.

Alternatives to consider

Jenkins + Allure Plugin

Native Jenkins integration with direct artifact archival; requires Jenkins infrastructure and manual job configuration but avoids containerization overhead for small teams.

TestNG/Pytest + Built-in HTML Reports

Native framework reporting (TestNG HTML, Pytest-html) eliminates Allure dependency and external infrastructure; simpler for projects without multi-project aggregation needs.

ReportPortal

Enterprise-grade test reporting with real-time dashboards, trend analysis, and multi-user collaboration; cloud/on-premise options available but higher operational complexity and licensing costs.

Software development agency

Build on allure-docker-service with DEV.co software developers

Deploy Allure Docker Service in minutes. Monitor test results in real-time, integrate with your CI/CD pipeline, and share reports across your team—all containerized and open-source.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

Related on DEV.co

Explore the category and the services that help you build with it.

allure-docker-service FAQ

Do I need to generate Allure results separately from my test framework?
Yes. Allure Docker Service only generates reports from pre-existing Allure-compatible result files. Your test framework must be configured to output results in Allure format (e.g., via TestNG/pytest/Cucumber plugins). See the referenced examples repository for framework-specific integration.
Can I use this in a multi-tenant SaaS environment?
Unknown. While multi-project support exists, data isolation, access control, and multi-tenancy safeguards are not explicitly documented. Security features must be explicitly enabled and verified before production deployment.
What happens if I disable security features in production?
The web UI, API endpoints, and report data will be publicly accessible to anyone with network access to the container. Always enable and properly configure authentication (login, roles) for production deployments.
How do I handle result retention and storage limits?
Storage optimization and history/trend retention are configurable but require explicit setup. Default behavior may accumulate large volumes over time. Review the 'Keep History and Trends' and 'Optimize Storage' documentation sections for your environment's storage constraints.

Work with a software development agency

Adopting allure-docker-service is usually one piece of a larger software development effort. As a software development agency, DEV.co provides software development services and web development expertise — pairing senior software developers and web developers with your team to design, build, and operate open-source testing software in production.

Start Automating Your Test Reports

Deploy Allure Docker Service in minutes. Monitor test results in real-time, integrate with your CI/CD pipeline, and share reports across your team—all containerized and open-source.