巡航控制 + Starteam:未拾取所有文件
我们的 CruiseControl 系统由 starteam 检查。 我注意到它有时不检查文件的新版本,只检查添加的文件。
有人知道为什么吗?
Our CruiseControl system checks out from starteam. I've noticed that it is sometimes not checking out new versions of files, only added files.
Does anyone know why this is?
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(4)
我无法说出为什么会发生这种情况,但无论如何,我们通过让 StarTeam 在签出之前删除所有本地文件来完全避免该问题。 我们通过这种方式获取所有文件。 我们在 NAnt 脚本中使用以下 StarTeam 参数:
其翻译结果如下:
I cannot say why this happens, but for what it's worth, we avoid the problem entirely by having StarTeam delete all of the local files before checking-out. We get all of the files that way. We use the following StarTeam arguments in our NAnt script:
Which translates to something like:
如果您使用的是 StarTeam Ant 任务,请检查您为包含和排除参数设置的内容,以确保您不会无意中限制签出的内容。
此外,强制和递归参数也可能值得关注。
您可以在此处查看结帐任务的完整说明:
http://nantcontrib.sourceforge。 net/help/tasks/stcheckout.html
If you are using the StarTeam Ant task, check to see what you have set for the includes and excludes parameters to make sure you are not unintentionally restricting what gets checked out.
Also the forced and recursive parameters may be something to look at as well.
You can see a full explanation of the checkout task here:
http://nantcontrib.sourceforge.net/help/tasks/stcheckout.html
这是一个 CI 构建,所以我想查看每个构建的差异,清理构建每次都会给我一个新的构建,但我不知道有什么新内容。
那么它是一个已知问题吗?
This is a CI build, so I want to see the diffs on each build, cleaning out the build gives me a fresh build each time, and I don't know what is new.
So its a known issue?
我最近遇到了同样的问题。 发生这种情况的原因与您在 GUI 中看不到过期文件或您有状态未知的文件(状态未更新)的原因相同。 因此,如果您更新文件的状态,它将能够从源代码管理中获取已更改的文件。 我们通过在配置文件中添加一个步骤来实现这一点。
I recently ran into this same issue. The reason this happens is the same reason you don't see out of date files in the GUI or you have a file with unknown status, the status is not updated. So if you update the status on your files it will then be able to pick up those files that have changed from the source control. We accomplish this by adding a step to our configuration file.