PluginStatsjenkins/ath has 280,554 recorded pulls on Docker Hub.
It ranks #323 of 1,263 tracked Docker Hub listings by pulls.
PluginStats has 3 daily observations since Oct 16, 2026; the latest is from Oct 18, 2026.
About jenkins/ath
Acceptance tests for Jenkins
End to end test suite for Jenkins automation server and its plugins.
The scenarios are described in the form of tests controlling Jenkins under test (JUT) through UI / REST APIs. Clean instances are started for individual tests to isolate the tests. The harness provides convenient docker support so integration tests can be written easily.
Getting Started
The simplest way to start the harness is calling BROWSER=firefox JENKINS_VERSION=2.73 mvn test. The complete test suite takes hours to run due to the number of covered components/use-cases, the cost of Jenkins setup, and selenium interactions. That can be avoided by selecting a subset of tests to be run - smoke tests for instance.
Further Reading
Running tests
The harness provides a variety of ways to configure the execution including:
• Selecting web browser • Specifying test(s) to run • Managing the versions of Jenkins and plugins • Using a http proxy • Prelaunching Jenkins • Selecting how to launch Jenkins • Obtaining a report of plugins that were exercised • Running tests in container • Running tests on Java 11 (WIP) • Debugging tests in container • Selecting tests based on plugins they cover (TODO)
Writing tests
Given how long it takes for the suite to run, test authors are advised to focus on the most popular plugins and use-cases to maximize the value of the test suite. Tests that can or already are written as a part of core/plugin tests should be avoided here as well as tests unlikely to catch future regressions (reproducers for individual bugs, boundary condition testing, etc.). Individual maintainers are expected to update their tests reflecting core/plugin changes as well as ensuring the tests does not produce false positives. Tests identified to violate this guideline might be removed without author's notice for the sake of suite reliability.
• Docker fixtures • Page objects • Mix-ins • Guice is our glue • Writing tests • Video tutorial by Kohsuke on how to write tests • Writing JUnit test • Testing slaves • Testing emails • Hamcrest matchers • How to use this from your own module • EC2 provider configuration • Investigation
Areas where acceptance-tests-harness is more suitable then jenkins-test-harness are:
• Installing plugins for cross-plugin integration • Running tests in a realistic classloader environment • Verifying UI behaviour in an actual web browser
Description from the Docker Hub listing.
Where jenkins/ath sits in the listing
Each band is one page of 20. Pulls on a log scale. Placement is projected from pulls, so it can differ from the marketplace's own sort order. Hover a dot to see the listing.
Charts
Images: 30d · 1y · all time · 1600×900 dark
Adoption over time
7/30/90-day growth
Filled points are observed values; hollow points come from Internet Archive snapshots of the listing page. Dashed segments span periods with no observations — values between points are not interpolated.
Recent observations
Full history (3)Similar Docker Hub plugins
Data source
Cumulative pull counts and stars come from the public Docker Hub API. Pulls count image downloads (including automated CI pulls), not installs or users.
Listing: https://hub.docker.com/r/jenkins/ath. First seen Oct 16, 2026; last successful collection Oct 18, 2026. See the methodology.