Child pages
  • LabeledTestGroupsPublisher Plugin

Due to some maintenance issues, this service has been switched in read-only mode, you can find more information about the why

and how to migrate your plugin documentation in this blogpost

Skip to end of metadata
Go to start of metadata

Plugin Information

View Labeled Test Groups Publisher on the plugin site for more information.

This plugin provides the functionality to group tests by types, such as "unit test", "smoke test", "regression test", etc.
This is useful for situations where different tests share the same test output format, but you want to display the results separately.

This plugin automatically converts JUnit Result Archiver and CPPUnit publishers to use the Labeled Test Groups Publisher. It automatically finds any jobs that use the JUnit Result Archiver, or CPPUnit publisher, and converts those publishers into groups within the "unit" group within a new Labeled Test Group Publisher. This conversion will not be persisted unless a job's configuration is explicitly edited by the user. The kinds of test result publishers that will be automatically converted are JUnit test result archiver and CppUnit test result archiver.

If you do not want your JUnit and CPPUnit publishers to be converted automatically, recompile the plugin with ENABLE_CONVERSIONS = false in

Coding Tasks

  • Fix reported tasks in the "Open Issues" JIRA.
  • Get rid of utilitybuilders.hpi plugins in test @LocalData's. There's a TouchBuilder in core now.
  • Look at EnhancedTestCase. Can it be eliminated? All of those methods should probably go into HudsonTestCase.
  • Lots of tests are marked SKIP_testFoo. I think they will mostly all work, though. Try turning them on and make sure.


Version 1.2.8 (Nov 20, 2015)

  • [JENKINS-30711] A bug where the parser name wouldn't load correctly is now fixed.
  • [JENKINS-20979] No more waiting on concurrent builds!

Version 1.2.7 (Mar 16, 2015)

  • Added the ability to configure test group labels. Free labels for everyone!
  • Updated the pom to have git instead of svn, jenkins-deployability, added current maintainer.

Version 1.2.6 (Mar 20, 2010)

  • Fixed problem where parser names were not showing up in the drop down menu.

Version 1.2.4

  • First public version


  1. Unknown User (prasadkunte)

    i there,

    I really liked the plugin. It is helping me segregate the test cases.

    I had a requirement though.

    In my blog on Restifying a legacy application, I have talked about implementing a right test pyramid (

    In my test pyramid I too have 6 difference levels. But they are: Unit, Business Logic/Domain Logic, Integration, Workflow, EndToEnd.

    In your plugin you have 6 levels as Unit, Smoke, Integration etc...

    In order to achieve my goal of having the names as I want, I downloaded the source code and made a small change (1 liner + test cases change) & now it really matches with my test pyramid. 

    I thought I should share it with you guys since the names suggested are really explicit and easy to understand. Here is how the plugin looks after the change

    Tell me what do you think about the same..


  2. Unknown User (asankeg2000)

    I have started to group my test using this plugin.

    I have provided a pattern to the  Report File Mask (Ex:  MyTestProject/test-output/TEST*.pkgnamepattern.*.xml)

    I want to create a group in such a way I will be having few groups and anything not falling to these patterns will go in to a goup call "Other" .

    How can I configure the    Report File Mask for that?


  3. Unknown User (fsteff)

    I just attempted labeled-test-groups-publisher 1.2.8 on Jenkins 2.50.

    In my build job I have lots of report publishers inside a Flexible Publish plugin section

    But right after installing, when I reopening the job, I found the entire Post-Build Actions section empty. :-(

    I were able to restore to an older version of the job, but only after uninstalling the plugin.

    Could this be made compatible with the Flexible Publish plugin?