Constraints to out-of-band modifications of project.xml and vcs-roots.xml?

I have quite a large number of interdependent build tasks that I wish to create (about 250), and I was wondering if I could do this by inserting the appropriate xml into the project.xml and vcs-roots.xml files. Specifically:

  • Can this be done live? How do I avoid clobbering anything teamcity tries to write there?
  • Are the vcs root ids and build config ids freeform, or do they have to be generated by teamcity?

I would welcome it if there was a programmatic API for me to do this...

1 comment

Christian,

> Can this be done live?

Yes, this can be done while the server is running.

> How do I avoid clobbering anything teamcity tries to write there?

There is no way to prevent data corruption in case of concurrent write, however, if nobody modifies anything from web UI and files are changed on disk only, it should work.
Anyway, pleae ensure you have backup of the current settings before any files modifications.

> Are the vcs root ids and build config ids freeform, or do they have to be generated by teamcity?
It's a good idea to use the same id patterns as TeamCity does and just to increment them from the current top values. Theoretically you can use any text ids for build configurations but I would not recommend this as they can be not supported well throughtout the system.
Adding new entities should work OK while the server is running, but I'd try restarting the server if anything does not not as expected before reporting the issue to us.

> I would welcome it if there was a programmatic API for me to do this...
You can vote for the feature.

0

Please sign in to leave a comment.