I'm testing a CI for a simple VS 2012 project with a Class project and a MS Unit Test Project.
I've setup a simple MSBuild task to build the MSUnit Test project and then run the unit tests via ContinuaCI.
When reviewing the Continua Configuration Build Log I find some unusual results. I'm not sure if it's me (stop laughing), or it's Continua. I've made the assumption that continua would "copy" all the outputs from all the projects to my Workspace\Output\UnitTests\ folder, based on the MS Build Action. Is this an incorrect assumption? What do I need to do?
We do not log what happens in the workspace sync process by default, because it can be a lot and it does impact on performance (on the continua build process it adds about 5 seconds, and a bit of a cpu spike). To enable it, edit the stage options :
After some more caffine, I suspect I may have misunderstood what you were asking for in the log for the sync info. I’ll have a look and see if it’s possible.
Just to clarify MSBuild Actions. If you configure Output Path = $Workspace$\Output\UnitTest</i> should that processing logic apply to all the MSBuild Compile targets? In this case I’m getting two projects correctly built, so I’m happy with that part of MSBuild actions.
If you look at the first image, you can see that target the MSTest child class project SyncWebServiceCall.proj copies the output to the workspace, defined in the Output Path, while the parent unit test project HighVolumeWSCall.Test.proj doesn’t then copy the output to $Workspace$\Output\UnitTest</i> defined.
I’ve highlighted in a green box the copy step for the first project compiled, while the second project compiled didn’t include that copy files step. I had expectations that the Output Path would copy all projects built using MSBuild to my workspace, or am I mistaken? Is that a better explanation of my confusion?
I’m not sure what is going on there. MSBuild only allows you to specify a single OutputPath property on the command line, what it does with that is up to msbuild and I don’t believe we have any control over that. Did you specify the configuration to build, perhaps not all the projects have that configuration?