Jenkins is a great communicator. It can consume the results of the tests generated by builds. Maven has a goal for site generation, where within the
pom.xml file, many of the Maven testing plugins are configured. The configuration is bounded by the
When run, a Jenkins Maven 2/3 software project Job does a number of things. It notes when a site is generated and creates a shortcut icon in the Jobs home page. This is a highly-visible icon that you can link with content.
You can gain fine-grained control of Maven site generation by triggering the Groovy scripts that structure sites in different Maven phases.