When Aggregating Downstream Test Results, it would be great to be able to use environmental variables when specifying which downstream job results to aggregate. Currently, if you use a variable, it doesn't resolve it and doesn't aggregate anything.
Details of my situation:
I have a job which calls a job which calls a job which dynamically generates and runs test jobs based on the contents of an SVN folder at a specified revision.
Automatic aggregation does not work even though test results are present in the individual jobs.
If I manually list the jobs to aggregate, they are successfully aggregated. However, because the list of job to run changes regularly, having a static list of jobs to aggregate is not a workable solution.
I have an environmental variable, $LIST_OF_TESTS, which is a comma-delimited string of all the jobs I need, but when I pass it into the 'Jobs to Aggregate' field, it does not work. I have tested that this variable is correct, and accessible from other post-build actions.