CruiseControl.net在任务更改后将文件提交到SVN [英] CruiseControl.net submit a file to SVN after a task has changed it

查看:78
本文介绍了CruiseControl.net在任务更改后将文件提交到SVN的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一个基于CruiseControl.NET的构建服务器和一个exec任务,可以在构建项目之前增加项目的程序集版本。我想知道,是否有办法(我不知道的CruiseControl.NET任务)将修改后的文件提交回SVN?



我需要它,所以当安装程序项目是手动构建的(我使用的是msbuld,因此不会连续构建),所有构建文件在部署时都将具有正确的程序集版本。哦,如果有人知道如何建立安装程序&



编辑:我非常想知道!



编辑:感谢Jonathan Stanton现在可以进行更新了,但是这会带来另一个问题...构建服务器现在会循环(更改时,它将更新程序集版本并提交文件。这会触发onModify触发器触发,因此它将更新程序集版本并提交文件...)。



我该怎么办,这样就不会循环?我可以添加更新SVN任务吗?

解决方案

关于stackoverflow的另一个答案是如何使用cfg cc来避免构建周期:
< a href = https://stackoverflow.com/questions/303511/cruisecontrol-net-how-to-checkin-code-during-the-build title =如何在构建过程中检入代码>如何检入代码在构建过程中


I have a CruiseControl.NET powered build server and an exec task that increments assembly version of the project before building it. I was wondering, was there a way (a CruiseControl.NET task I don't know about) to submit that modified file back to SVN?

I need it so when the setup projects are built manually (I am using msbuld so those aren't built continuously) all the build files will have the correct assembly versions on deployment. Oh and if someone knows how to build setup & deployment projects on a build server without Visual Studio installed, I'm dying to know!

EDIT: Thanks to Jonathan Stanton the update now works, however it creates another problem... The build server now loops (on change it updates assembly version and commits the file. This caouses the onModify trigger to fire so it updates assembly version and commits the file...).

What can I do so it won't loop? Can I add an update SVN task? Will that help?

解决方案

There's another answer on stackoverflow about how to cfg cc to avoid the build cycle: How to checkin code during the build

这篇关于CruiseControl.net在任务更改后将文件提交到SVN的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆