4 comments
Comment actions Permalink

I guess the only way that appears to work is to quiesce TeamCity, modify the project.xml files to surgically insert the build tasks and their dependencies, and then hope for the best.

Even though the docs appear to imply that it is safe to modify those files while TC is running, we did have some very bad experiences doing just that.

Again - what do people do? Do they really sit there for 30 minutes clicking away to get a set of build tasks configured?

0
Comment actions Permalink

Hi Christian

Templates could help.

But I do understand this is not universal solution. We have TW-8394 request, please vote.

Michael

0
Comment actions Permalink

Is the API used by the Web UI documented someplace? Or is it subject to rapid change between versions?

One simple thing that may help a lot is if one could inherit from multiple templates, in a definable order.

For example, I would have at least a platform template and a build type template - but that would not resolve the most painful part: adding the dependencies. I mean, really: we have 1500 build configs - every time we want to add an artifact dependency, some poor soul needs to scroll through a 1500 element dropdown...

0
Comment actions Permalink

Hi Christian

Yes, URLs used in web UI are not docummented. There are some examples at Accessing Server by HTTP page, but it doesn't cover creation of new items.

Good news about artifact dependencies is the dialog has been updated in version 6.5, and supports search.

Michael

0

Please sign in to leave a comment.