How to not need a new build for any new project/solution
Hello
First, I am new to TeamCity lets say less than 3 hour of experience. With this in mind, I have installed TeamCity and made my first project and build. I use SubVersion and have two .sln projects. When I Add a new Build Step Visual Studio (sln) I need also to select "Solution file path" which navigate to the current csproj file. As far as I understand I then need a new Build Step for each new sln project I add to my repository in order for TeamCity to do a build .. are there any way to let TeamCity find the individual csproj files, meaning that I basically can add new projects then expect TeamCity to handle to do the build. If not it seems as there will be an overhead always to make sure all needed builds are manually added - is this how it should be? or am I missing something here ?
Thank you for your help.
Kind regards,
Danny Nielsen
Please sign in to leave a comment.
Hi Danny,
If your projects don't have a solution that joins all of them, teamcity will not automatically do it for you, as you have experienced, so if your projects are separate, then yes, you will need to add further build steps to build them.
Depending on how your projects work with each other, it might be better to have them as separate build configurations, if you have multiple build agents, that would mean that they can be run in parallel, while build steps will always be taken sequentially. If you generate artifacts (such as libraries or executables) that are needed by others, you can join them via dependencies, snapshot for ordering: https://www.jetbrains.com/help/teamcity/snapshot-dependencies.html and artifact for dependencies on files: https://www.jetbrains.com/help/teamcity/artifact-dependencies.html