Publishing multiple projects

Hi,

Basically internally we have the following use case which I would regard as fairly basic:

We have many client projects (maybe 5 at any given point in time), which we wish to automatically publish to our servers using TeamCity and a rake script.

The problem is, that as far as I can tell, I would have to create a TeamCity project for every single client project despite the fact that the publishing will be almost identical from one project to another. I thought perhaps I could attach multiple repositories to a single project but if I attach something like 10 repositories, every time it publishes just one site, it will actually completely check out every other repository attached to the Teamcity project which is undesireable.

The best solution would allow me to setup one TeamCity project which monitors multiple repositories. Whenever it detects a checkin, it only checksout the repository with the activity and carries out the publishing mechanism. Does anyone have experience doing something like this?

Thanks,
Ed

5 comments
Comment actions Permalink

Correct me if I'm wrong, but it should only check out changes by default if you attach multiple reposotories, unelss you have "clean sources on build" (IIRC) checked.

0
Comment actions Permalink

Hi William,

Thanks for the input. OK that eases my concern about pulling to much information from the repository. However for me to publish the correct repository I would need to know which repository caused the checkin so that my rake script can publish the correct project. I haven't been able to find any properties that I can expose to the publish script that will help me do this.

Thanks,
Ed

0
Comment actions Permalink

Hi Edward

Did you consider to use templates?
You could create a single template with common set of options, and inherit five build configurations from it. In such way, all build history is split between projects, but common settings can be changed in one place.

Michael

0
Comment actions Permalink

Hi Michael,

Thanks for the suggetion. But I am not sure it fits too nicely. I would want any changes made to the project to apply to all the projects. Some options would not be updated when changing settings from one project to another. I am thinking since these particular projects don't require so much validation on the testing front a build server might be overkill. I am playing with chef from www.opscode.com to see how that fits into my needs.

Thanks,
Ed

0
Comment actions Permalink

Hi

Configuration Parameters can help to set unique values in configurations inherited from the same template.

0

Please sign in to leave a comment.