CruiseControl + Starteam: do not collect all files

Question

Our CruiseControl system checks from the beginning. I noticed that sometimes not checking for new versions of files, but only adding files.

Does anyone know why this is?

Answer 1

I can’t say why this is happening, but for what it's worth, we completely avoid the problem of StarTeam deleting all local files before checking. Thus, we get all the files. We use the following StarTeam arguments in our NAnt script:

delete-local -q -p "${starteam_project_root}" -is -filter "N" -cfgd "${exec_time}" 

This means something like:

 delete-local -q -p "user: passwd@SERVER :49201/ProjectName/" -is -filter "N"-cfgd "09/18/2008 14:33:22" 

Answer 2

I recently ran into this problem. The reason this happens, for the same reason that you do not see obsolete files in the GUI or you have a file with an unknown status, the status is not updated. Therefore, if you update the status in your files, it will be able to receive files that have been changed from the control. We accomplished this by adding a step to our configuration file.

  <prebuild> <exec> <executable>C:\Program Files\Borland\StarTeam Cross-Platform Client 2006 R2\stcmd.exe</executable > <buildArgs>update-status -nologo -is -q -p "username: password@192.168.0.1 :49201/Code Project/Code Path" -fp "C:\projects\My Code Directory"</buildArgs> <buildTimeoutSeconds>0</buildTimeoutSeconds> </exec> </prebuild> 

Answer 3

This is a CI assembly, so I want to see the differences in each assembly, cleaning the assembly gives me a new assembly every time, and I don't know what's new.

So this is a known issue?

Answer 4

If you use the StarTeam Ant task, check what you specify for the includes and excludes parameters to make sure that you are not arbitrarily not restricting the output.

In addition, forced and recursive options can be considered as well.

Here you can see a full explanation of the verification task:

http://nantcontrib.sourceforge.net/help/tasks/stcheckout.html