This is not currently supported by the Jazz SCM pre-build participant, though I've asked the SCM team if there's a debug option for this and will let you know if so.

Is this just to get a better handle on progress, or is there some other reason for wanting the exact list of files?

Depending on your use case, you may be able to use the SCM command line tool to figure out what's changed between builds, but this would be done in the script after the load had completed.

For example:
scm login -r https://localhost:9443/jazz -u ADMIN -P ADMIN
scm list snapshots -r https://localhost:9443/jazz build
scm compare -r https://localhost:9443/jazz -I f snapshot 1190 snapshot 1191

Where:
- 'build' is the name of the build workspace
- 1190 and 1191 are the short ids, aka aliases, assigned by the SCM CLI to refer to the listed snapshots
- the '-I f' option tells it to list filesystem changes instead of the default of listing change sets

You can also drive it in terms of item ids (UUIDs) instead of aliases, which is recommended when being used automatically like in a build script:

scm --non-interactive -u y -a n list snapshots -r https://localhost:9443/jazz build
scm --non-interactive compare -r https://localhost:9443/jazz -I f snapshot _oJ298EnuEd65TJqMHrNQhg snapshot _5aomEEjZEd6Wfr6_eaM_mg

Since this is based on comparing snapshots for the builds, it would describe what changed in the repository workspace, not necessarily what got loaded onto disk (though they should normally correspond).

Note that the Jazz SCM pre-build participant publishes the UUID for the snapshot (if there is one) into the team.scm.snapshotUUID property, so an Ant script can substitute it with ${team.scm.snapshotUUID}.

The UUID for the previous build's snapshot is not published, so this would need to be managed by the script.

It really depends on what you want to do with this info, so more details about your use case would help.

Hi,
I also need some verbose option for the fetch step.
I have some annoying timeout exception:
2012-04-05 14:25:18 Fetching files to fetch destination "D:\Workspace\build_Utah_Sanity" ...
CRRTC3524W: Repository connection failed: CRJAZ0099I When accessing the URL "https://my_url.com:443/jazz/service/com.ibm.team.filesystem.common.IFilesystemService" the following HTTP error occurred: "java.net.SocketTimeoutException"

And we don't know how to debug it.
Any idea?
This problem comes and goes, and we guess it is connected to load level of the server / comm / whatever.
Thanks.
Hagit

Is there a way to instruct the Jazz SCM fetch task in 2.0.0.1 that is part of the build process to verbosely output the files that were fetched?

This would be via the standard Jazz SCM prebuild participant during an ant or command line build. It would be very helpful for debugging problems if the fetch participant could output every file downloaded or replaced in the local workspace to the build log.

E.g.

2009-11-25 21:52:28 Should build occur?
Checking for changes incoming to workspace "LC3.0-share_wsbuild_ws_checkpoint" ... found changes (5)
2009-11-25 21:52:29 Yes: Pre-build participant "com.ibm.team.build.jazzscm" would like to build.
2009-11-25 21:52:29 Invoking pre-build participant "com.ibm.team.build.jazzscm"
Accepting changes into workspace "LC3.0-share_wsbuild_ws_checkpoint" ...
Fetching files to fetch destination "/home/wsbuild/B_LCS3.0-checkpoint" ...
Downloading /file1/example1
Downloading /file1/example2
etc....

Is this possible in 2.0.0.1?