2012/9/21 Kenneth <kenneth.f.niel...@gmail.com> > Do I need to have both projects in the job? - I dont want to, it will be > like 15 projects in each job. > how do I handle it? >
I do not get your question completely. So, what do you want to achieve? You want to compile a unit test project and run its tests afterwards? Easiest way: compile the complete solution via msbuild plugin, run the test project for each unit test project you have. If compiling takes a significant amount of time and you have lots of test projects and have lots of CPUs in parallel, you could take my approach: Have one job which compiles your complete solution, let it harvest all the artifacts via clone-workspace-scm plugin and start a job for each test project to run your tests. HTH dirk > Target CoreClean: > Deleting file > "C:\Jenkins\jobs\LimeUtilitiesUnitTests\workspace\obj\Any > CPU\LimeUtilitiesUnitTests.csproj && exit > %0%\Debug\ResolveAssemblyReference.cache". > > Target ResolveProjectReferences: > C:\Windows\Microsoft.NET\Framework\v2.0.50727\Microsoft.Common.targets > : warning : The referenced project '..\LimeUtilities\LimeUtilities.csproj' > does not exist. > Done building target "ResolveProjectReferences" in project > "LimeUtilitiesUnitTests.csproj". > Target CoreCompile: > C:\Windows\Microsoft.NET\Framework\v2.0.50727\Csc.exe /noconfig > /nowarn:1701,1702 /reference:"obj\Any CPU\Debug\nunit.framework.dll" > /reference:"C:\Program Files\Reference > Assemblies\Microsoft\Framework\v3.5\System.Core.dll" /reference:"C:\Program > Files\Reference > Assemblies\Microsoft\Framework\v3.5\System.Data.DataSetExtensions.dll" > /reference:C:\Windows\Microsoft.NET\Framework\v2.0.50727\System.Data.dll > /reference:C:\Windows\Microsoft.NET\Framework\v2.0.50727\System.dll > /reference:C:\Windows\Microsoft.NET\Framework\v2.0.50727\System.Xml.dll > /reference:"C:\Program Files\Reference > Assemblies\Microsoft\Framework\v3.5\System.Xml.Linq.dll" /debug+ > /out:"obj\Any CPU ./LimeUtilitiesUnitTests.csproj && exit > %0%\Debug\LimeUtilitiesUnitTests.dll" /target:library > LimeCommandChecksumTests.cs LimeCommandTests.cs Properties\AssemblyInfo.cs > ULimeCommunicationTests.cs > LimeCommandChecksumTests.cs(2,7): error CS0246: The type or namespace > name 'LimeUtilities' could not be found (are you missing a using directive > or an assembly reference?) > LimeCommandTests.cs(2,7): error CS0246: The type or namespace name > 'LimeUtilities' could not be found (are you missing a using directive or an > assembly reference?) > > On Friday, September 21, 2012 10:29:15 AM UTC+2, Kenneth wrote: > >> I get this error message when jenkins build c# projects that depend on c# >> dll, that I've made in another job. >> In visual studio I've made the project refer the other project, to make >> it behave in release and debug builds. >> but it causes jenkins to fail... >> >> ... >> Target ResolveProjectReferences: >> C:\Windows\Microsoft.NET\**Framework\v2.0.50727\**Microsoft.Common.targets >> : warning : The referenced project '..\LimeUtilities\**LimeUtilities.csproj' >> does not exist. >> Done building target "ResolveProjectReferences" in project >> "LimeUtilitiesUnitTests.**csproj". >> Target CoreCompile: >> C:\Windows\Microsoft.NET\**Framework\v2.0.50727\Csc.exe /noconfig >> /nowarn:1701,1702 /reference:"obj\Any CPU\Debug\nunit.framework.dll" >> /reference:"C:\Program Files\Reference Assemblies\Microsoft\** >> Framework\v3.5\System.Core.**dll" /reference:"C:\Program Files\Reference >> Assemblies\Microsoft\**Framework\v3.5\System.Data.**DataSetExtensions.dll" >> /reference:C:\Windows\**Microsoft.NET\Framework\v2.0.**50727\System.Data.dll >> /reference:C:\Windows\**Microsoft.NET\Framework\v2.0.**50727\System.dll >> /reference:C:\Windows\**Microsoft.NET\Framework\v2.0.**50727\System.Xml.dll >> /reference:"C:\Program Files\Reference Assemblies\Microsoft\** >> Framework\v3.5\System.Xml.**Linq.dll" /debug+ /out:"obj\Any CPU >> ./LimeUtilitiesUnitTests.**csproj && exit >> %0%\Debug\**LimeUtilitiesUnitTests.dll" >> /target:library LimeCommandChecksumTests.cs LimeCommandTests.cs >> Properties\AssemblyInfo.cs ULimeCommunicationTests.cs >> LimeCommandChecksumTests.cs(4,**7): error CS0246: The type or namespace >> name 'LimeUtilities' could not be found (are you missing a using directive >> or an assembly reference?) >> ... >> >> should I do a matrix build, to get a release and debug version of the >> xxxxUtilities.dll that I use in my unit test job? >> I use the copy from artifact plugin, with these params: >> >> >> Project name:LimeUtilities >> Which build:Latest succeful build >> Artifacts to copy: blank >> Target directory: .\ >> >> In the LimeUtilities I have a post build task that Arkives the artifacts >> Files to arhive: obj/Any CPU/Debug/LimeUtilities.dll,**obj/Any >> CPU/Debug/LimeUtilities.pdb ///// these are only the debug ones.. maybee I >> should archive the release to. >> Exclude: blank >> I currently only build debug in jenkins. >> >> How do I fix that? >> >> >> >
