Analyze broken builds - alternatives to log file
One answer
Hi Karen,
the temporary files would be at the file system location the build is running. One way to approach that would be to copy the build result into a folder that is related to the build and contains the data as long as it is not deleted. This would be also an approach for keeping the build results for later deployment.
With command line SCM, I assume you could also check in the data into the RTC SCM system. The penalty would be the increasing size of the repository.
Ralph
the temporary files would be at the file system location the build is running. One way to approach that would be to copy the build result into a folder that is related to the build and contains the data as long as it is not deleted. This would be also an approach for keeping the build results for later deployment.
With command line SCM, I assume you could also check in the data into the RTC SCM system. The penalty would be the increasing size of the repository.
Ralph
How can we watch into the code base (e.g. the snapshot) including temporary files that were created during the build?
In Clearcase we do a build on a dynamic view which can be started on a developers machine when the build brakes.
A log file is not enough in many situations.