Hi, we have an need to add many (40-50) solutions that all should be configured to build the same way.
Is there a way to do this? Self code through an API or some features in the GUI by having general solution template or the like.
Just a note: we have written a Build.cmd file that is using the continua logger, so we have the metrics too. this way we build the same on the developer machines as on the build server.
Hi Christian
So this is supposed to help us compile the same way, but we still have to setup each and every solution manually in Continua right?
Do you have some way of handling this?
Hi Thomas
Are these solutions related? Are they all in the same repository? You haven’t really provided enough information to understand exactly what it is you need to do.
Ok, I’ll try to elaborate.
Currently all solutions are in the same perforce repository.
They should be build separately but with the same process steps, for instance [1] check some structure, [2] build solution, [3] release to a nuget stream.
Our issue is that we think there will be many small solutions and we want to manage them separately, but we think it is a hassle to add them all one at a time in continua.
So our the dream scenario is as follows:
1) New solution file (.sln) is added to perforce
2) We login to continua, create a new configuration based on our base configuration, write the path to the solution file, all is setup for that build.
3) Continua now monitors that solution and all files underneath it and rebuilds the solution if needed.
In general we just want it to be quick and easy to get from 1) new solution added to a repository to 2) solution is being monitored and build. There should be as few manual steps as possible in this.
In that case it’s simple, create the first configuration, once it’s working as desired, clone the configuration (from the project wizard final page), edit new configuration stage to point to the new solution file, click save and exit.