我可以对 CruiseControl.NET 项目配置进行参数化，以便通过 Web 界面公开参数吗？
我目前正在尝试使用 NAnt 和 CruiseControl.NET 来管理我的软件开发的各个方面。 目前，NAnt 几乎可以处理所有事情，包括根据我在命令行上指定的输入目标替换环境特定设置（例如数据库连接字符串）。
CruiseControl.NET 用于在提交新代码时为默认环境(dev)构建应用程序。 我还希望 CruiseControl.NET 为我的附加环境测试和阶段调用构建，但我不希望每次（每天）调用开发构建时自动调用这些构建，因为测试和阶段部署发生的频率要低得多。 仅当应用程序准备好进行 QA 时，才会进行测试和阶段部署。
我可以通过指定多个项目（每个环境一个）来轻松地做到这一点。 但是，我已经配置了许多项目，每个项目对应我的应用程序中的每个里程碑。 如果我必须为每个里程碑设置 3 个项目，则 CruiseControl.NET 配置可能会很快失控。
这是我的问题： 我可以对 CruiseControl.NET 项目配置进行参数化，以便通过 Web 界面公开参数吗？
（我认为）我最好可以为 Web 界面中公开的每个环境（例如，开发、测试、阶段）设置复选框。 将为每个检查的环境进行构建，无论构建是强制的还是自动的。 如果我可以默认选中状态就更好了。
I am currently trying to use NAnt and CruiseControl.NET to manage various aspects of my software development. Currently, NAnt handles just about everything, including replacing environment specific settings (e.g., database connection strings) based on an input target that I specify on the command line.
CruiseControl.NET is used to build the application for the default environment (dev) anytime new code is committed. I also want CruiseControl.NET to invoke a build for my additional environments test and stage, but I do not want these to be automatically invoked every time that a dev build invoked (daily) as test and stage deployments happen far less frequently. Test and stage deployments only occur when the application is ready for QA.
I can easily do this by specifying multiple projects, one for each environment. However, I already have many projects configured, one for each milestone in within my application. If I have to setup 3 projects for each milestone the CruiseControl.NET configuration can get out of hand quickly.
Here is my question:
Can I parameterize a CruiseControl.NET project configuration such that the parameters are exposed by the web interface?
Preferably (I think), I could have checkboxes for each environment (e.g., dev, test, stage) exposed in the web interface. A build would be made for each environment that is checked, whether the build was forced or automatic. It would be even better if I could default the checked state.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
此功能（动态构建参数）目前正在 1.5 中开发，您可以在 睡梦。 这是描述该功能的帖子。
This feature (Dynamic Build Parameters) is currently being worked on for 1.5, and you can try it out in the nightlies. Here's a post describing the feature.
正如 Scott 所提到的，这是不可用的，但只需编写一个小模板，然后以邮件合并类型的方式自动生成给定模板和环境列表的 ccnet.config 文件，就不需要太多了。
As Scott has mentioned, this isn't available, but it wouldn't take too much just to write a little template and then auto-generate the ccnet.config file given that template and a list of environments in a mail-merge type way.
不幸的是，您无法使用 CruiseControl.NET 执行类似的操作。 这是个好主意，因此您可能希望将其作为功能请求提交。
Unfortunately, you can't do anything like that with CruiseControl.NET. It's a good idea, so you might want to submit it as a feature request.
现在从 Cruisecontrol 1.5 开始完全支持： http://cruisecontrolnet.org/projects/ccnet/wiki /参数
This is fully supported now starting with cruisecontrol 1.5: http://cruisecontrolnet.org/projects/ccnet/wiki/Parameters