Child pages
  • Build Flow Test Aggregator Plugin
Skip to end of metadata
Go to start of metadata

Build Flow Test Aggregator is the simplest way to aggregate test results from builds started dynamically by the build flow job. It's a post-build step that only shows up for build flow projects.

Plugin Information

No information for the plugin 'build-flow-test-aggregator' is available. It may have been removed from distribution.

Overview

Normally to aggregate test results Jenkins has to "understand" the upstream - downstream dependencies between jobs. This can be achieved by generating an artifact in job1 and fingerprinting that archive from all the downstream jobs. But even then you'd have to have a separate job where you aggregate test results, which is not convenient.

Build Flow Test Aggregator simply loops over all of the builds scheduled by a flow run and retrieves and aggregates test results if there are any. The test results will be available just like any other test results, it will show aggregated results and statistics, with links to each individual test for further inspection:

Configuring

To configure test aggregation you need to set the "Flow run needs a workspace" checkbox:

Then just enable the "Aggregate build flow test results" post-build action:

Changelog

Version 1.2 (Aug 31, 2015)

  • Added configurable test results trend chart.
  • Added support for aggregating test results from Maven module builds.
  • Fixed handling project renaming and deleting.
  • Fixed direct links to failed tests on test results summary page.

Version 1.1 (Apr 18, 2015)

  • Fixed a NPE caused by not retrieving project by its full name.
  • Test results are now shown by the builds' full name, enables seeing build parameters etc right from the results page.
  • Added support for aggregating test results from MultiJob and matrix builds as well.
  • Added support for recursively aggregating test results from started flow jobs and MultiJob-s.

Version 1.0 (Nov 07, 2014)

  • Initial release of the plugin.
  • No labels

8 Comments

  1. note: I am using folders/subfodlers in my setup.

    I have a build flow like this:

    branch='current'
    
    viewmap="//foo/${branch}/new_test/... //foo/src//${branch}/new_test/..."
    
    parallel(
       { build("ui-test-demo", branch:branch) },
       { build("ui-test-demo-2", branch:branch) },
    )

    I seem to be getting this error

  2. Feature Request: Would it be possible to get the trends reports as well?

  3. Maybe it's the same as Ali requested, but I miss the graph on the flow-job status pqge with the number of tests (total/failed)

  4. I have  BulidFlow like this

    out.println 'Checking out & creating workspace and TestDrive T:'
    build( "workspace_checkout" )
    ignore(UNSTABLE) {
    betaSuite =build ("suite_test", suiteToTest: "T:/TestLab/betaSuiteTests.xml" )
    }
    ignore(UNSTABLE){
    availabilityTest =build ("suite_test", suiteToTest: "T:/TestLab/AvailabilityTest.xml" )
    }

    Test results are showing as per build job. My job is parameterized for different tests. 

    Is there any way to change the job name in the aggregated test results?  

  5. Hi,

    is there any possibility to aggregate the results from another flow job (which has aggregated results) and from multijob?

    Example:

    Flow-1

    • jobA
    • jobB

    JobC

    JobD

    ---------

    Flow-2

    • Flow-1
    • JobC
    • JobD

    Only results from JobC and JobD are aggregated at Flow-2 (the same situation happens with the multijob).

    Thanks for any updates!

      1. I've released version 1.1 of the plugin that addresses many of the requests. See the full changelog from: https://github.com/zeroturnaround/build-flow-test-aggregator. Also with any future requests, I strongly recommend to post them on GitHub, because there I get notifications, otherwise I might miss some requests/comments.

  6. Hi,

    Can we use TestNG report for aggregation?

    Thanks,
    Sathis M R