Is there any way possible this information could be made available during project execution?

Problem Statement:
- pool of machines
- selector has all the machines as valid
- project starts and threads x compiles across the pool y machines
- aggregate step runs on same pool and needs result info from the machines that participated.

That's an interesting idea - I'll take that as an RFE to our dev team.

In the meantime, you could accomplish this in two ways:
1) From the aggregate step, make an API call back into BF to retrieve
the list of results, retrieving the server information from the ones
that are siblings to your aggregate's result.
2) From each (presumably broadcast) step, echo out your server
information (provided to you in the environment) to a file in a
shared location for later retrieval.

Of the two, I would prefer the first as it is immune to timing issues that you would have to deal with using the second approach.

Is there any way possible this information could be made available during project execution?

Problem Statement:
- pool of machines
- selector has all the machines as valid
- project starts and threads x compiles across the pool y machines
- aggregate step runs on same pool and needs result info from the machines that participated.

That's an interesting idea - I'll take that as an RFE to our dev team.

In the meantime, you could accomplish this in two ways:
1) From the aggregate step, make an API call back into BF to retrieve
the list of results, retrieving the server information from the ones
that are siblings to your aggregate's result.
2) From each (presumably broadcast) step, echo out your server
information (provided to you in the environment) to a file in a
shared location for later retrieval.

Of the two, I would prefer the first as it is immune to timing issues that you would have to deal with using the second approach.

An RFE work item has been created in our public project area :

https://jazz.net/jazz08/resource/itemName/com.ibm.team.workitem.WorkItem/16868