How to configure svn Task in CruiseControl.net to detect subversion external changes

I have a .net project in subversion that integrates seamlessly with Cruisecontrol.net.

I am using the CCN task to control the source of SVN.

A .net project library directory with a set of reusable components configured as external subversions.

ProjectA \ libraries {reusable components directory} ProjectA \ libraries \ COMPONENT1 ProjectA \ libraries \ COMPONENT2 ProjectA \ libraries \ Component3

projectA \ Src {source code directory}

when the external subversion variables are changed, the assembly does not start because it does not detect changes that have occurred in extern folders.

How to make the ccnet subversion task build right away when there are changes to the configured components as external.

+4
source share
3 answers

CruiseControl.NET 1.4 has several new flags for the subversion source control block, one of which is CheckExternals, which sets this to true in your configuration, and any changes in your external files should trigger the build.

<checkExternals>True</checkExternals> <checkExternalsRecursive>True</checkExternalsRecursive> 
+7
source

I just set up the polling interval to test the mods - using the node triggers in ccnet.config is the Trigger interval. I also say that it should only be built if modifications exist (the svn source has been changed) using the IfModificationExists attribute (which is the default)

You can set this interval pretty low if you want, but I'm not sure how to get the notification from SVN that ccnet receives.

0
source

Thanks to Alex for the answer.

we also started using a Relative external URL, which does not work with CCNET 1.4,

it does not work when trying to get a list of changes.

and also I see another problem with this CheckExternals code.

(i.e.) when external elements are configured from different svn repositories.

and the external library is changed only, and also the history command will not be executed.

0
source

All Articles