由于分支上设置的更改，CCNET Trunk 开始构建
我将 CCNET 与 Mercurial 结合使用。我有一个项目，有一个分支和一个头。它们都在 CCNET 中配置。该分支运行良好，仅当该分支发生更改时才开始构建。
每次检查修改时，主干（称为默认）都会开始构建，因为它“看到”分支的更改集。它不会检查它们（很好的想法），但它每次都在不断构建。
如何避免主干项目看到分支的变更集？
http://repository/hg/hgwebdir.cgi/projectsname/ D:\projects\projectsname <分支>默认
I am using CCNET in combination with Mercurial. I have a project that got a branch and a head. they are both configured in CCNET. The branch is running fine, it only start building when there are changes on this branch.
The trunk (called default) starts building every time modifications are checked, because it "sees" the change sets of the branch. It doesnt check them out (good think), but it keeps building every time.
How can I avoid the trunk project seeing the changesets of the branch?
<sourcecontrol type="hg"><repo>http://repository/hg/hgwebdir.cgi/projectsname/</repo><workingDirectory>D:\projects\projectsname</workingDirectory><branch>default</branch></sourcecontrol>
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
听起来您发现了一个 CCNET bug，但以防万一以后有帮助，如果您希望 CCNET 仅拉取特定的命名分支，您可以使用此表示法作为您的存储库 URL：
来自
hg help urls:当然，这是假设 CCNET 正在幕后使用 Mercurial，但这是一个相当安全的赌注。
这样做将导致您的 CCNET 仅克隆并跟踪具有该分支名称（仍可能包含多个头）的变更集。
It sounds like you found a CCNET bug, but in case it's helpful later, if you want CCNET pulling down only a specific named branch you can use this notation for your repo URL:
Which comes from
hg help urls:That assumes, of course, that CCNET is using mercurial under the covers, but that's a pretty safe bet.
Doing that will cause your CCNET to only clone down and track changesets with that branch name (which still could include multiple heads).
嗯，我看起来这是一个 CCNET bug，我在默认情况下添加了一个变更集，现在它每 30 秒停止构建一次
Hmm I looks like this is a CCNET bug, I added a changeset on the default and now it stopped building every 30 seconds
该错误目前正在修复中
http://groups.google.com/group/ccnet-devel/t/fe3f768a346a3796
所以任何测试方面的帮助都是值得赞赏的:-)
this bug is currently being worked on
http://groups.google.com/group/ccnet-devel/t/fe3f768a346a3796
so any help with testing is appreciated :-)