Worked examples for the v5 Build-Template feature?

Are there any worked examples for the Build-Template feature?

What I specifically want to do is make it easy to set up CI for branches.  We have a config set up that uses (svn) trunk, but would like to be able to set up a config that runs on a branch.  However, it _looks_ like this would require that each developer be an administrator, because only administrators can edit VCS settings (I think).  This isn't really desirable, but it _is_ desirable that developers be able to set up branch-builds.

The only thing that really needs to differ in the branch-build config is one (or two) of the VCS roots.  But reading the docs suggests that VCS' are not template-able...?

For example:
Trunk config:
http://svn.local/svn/Foo/trunk

Branch config:
http://svn.local/svn/Foo/branches/issue-343

I'd want to be able to do something like
Templated VCS root:
http://svn.local/svn/Foo/${config.svnroot}
and supply config.svnroot as a configuration property (though I'm not sure that's the term in TeamCity, yet)

I realise that the documentation I linked to supplies a workaround for what I want to do - I don't want to use this, because I don't want each build-config to potentially check out the entire repository, since this will be far too slow.  Exclude checkout rules with svn will check out the whole thing, then delete the parts that are excluded.

1 comment
Comment actions Permalink

Actually you can have one VCS root for the Foo project: http://svn.local/svn/Foo
And use checkout rules to checkout trunk or branch:
+:trunk=>.
+:branch=>.

In TeamCity 5.0 parameters are supported in checkout rules, i.e. you can specify:
%checkout.rules%
for checkout rules in template and in concrete configuration you can specify specific value for checkout.rules configuration parameter.

0

Please sign in to leave a comment.