change set includes hostnames? why?
We switched to using VM login hosts, meaning user may log into different host on different days, and we found an unusual behavior. All our developers upload their changes from a linux commandline usi...
Forum Discussion
The main difference between using addchanges and addcvsdiffs is the amount of metadata you get. When using addchanges, we connect to the CVS server, and, as a result, are able to get more meta data. While using addcvsdiffs, you get less metadata because we do not contact the CVS server.
You are correct that using addchanges will catch the hostname of the
machine from which the changes are uploaded. For Perforce and
Subversion, we have server integration that will allow you to map the machines so that they show as part of the same repository, and that eliminates the issue you are
seeing. (For more information on the mapping with Perforce and
Subversion, see Client Configuration Mapping at
http://codecollaborator.smartbear.com/docs/manual/6.0/index.html?admin_version_control.html.)
With CVS, however, we have no way of pulling out the machine names and thus are unable to map them to one CVS server. A suggested workaround is to use addcvsdiffs exclusively.
You are correct that using addchanges will catch the hostname of the
machine from which the changes are uploaded. For Perforce and
Subversion, we have server integration that will allow you to map the machines so that they show as part of the same repository, and that eliminates the issue you are
seeing. (For more information on the mapping with Perforce and
Subversion, see Client Configuration Mapping at
http://codecollaborator.smartbear.com/docs/manual/6.0/index.html?admin_version_control.html.)
With CVS, however, we have no way of pulling out the machine names and thus are unable to map them to one CVS server. A suggested workaround is to use addcvsdiffs exclusively.
