Build machine compilation error.

Sep 23, 2010 at 10:52 AM

Ok, despite my normal way of keeping build machines clean (VS free) I have a machine setup with VS 2010 and the sdk.  I am getting an error creating the VSIX.

This is the first time I have automated a VSIX project, so anyone have any idea as to why I am getting this error?  I can manually build the solution without a problem.  I am running the build.cmd, from davids fork, I got the same error when I had msbuild run the .sln file directly.

GetVsixDeploymentPath target) ->

[15:49:14]: C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0\VSSDK\Microsoft.VsSDK.targets(378,5): error : Error trying to read the VSIX manifest file "obj\Debug\extension.vsixmanifest". The system cannot find the file specified. (Exception from HRESULT: 0x80070002) [C:\TeamCity\buildAgent\work\728049ed4a736ff3\NuPack.Tools\NuPack.Tools.csproj]
Developer
Sep 23, 2010 at 4:57 PM

64 bit machine? 64 bit powershell window? I've seen some issues with some of our devs internally building the vsix files. But the error above says file not build. Try running each target manually and see what happens.

Sep 23, 2010 at 8:20 PM

It is a x64 box. But the solution builds through visual studio. I may just need to restart the agent services. That paths may not be totally loaded from the install.

Developer
Sep 24, 2010 at 6:48 AM

Any word on this?

Sep 24, 2010 at 11:41 AM

I got it working. I hade to run the agent under a user profile. Next we need to read the version number from an env variable. Then we can auto publish the trunk bits.

On Sep 24, 2010 1:48 AM, "dfowler" <notifications@codeplex.com> wrote:
> From: dfowler
>
> Any word on this?
>
>
Developer
Sep 24, 2010 at 4:38 PM

Sweet!

Sep 24, 2010 at 4:57 PM

We are looking good. I have the build with access to the main repository. The only part that is currently failing is the ILMerge.  Below is the output.  I do not have access to the build machine from my office, but I will check into is a little later today.  We are getting really close on having this fully functional.

 ILMergeTheExecutable:
[21:52:33]:   ILMerging the executable contents in C:\TeamCity\buildAgent\work\abd984c9980eb3a7\Build\..\bin\NuPack\Console
[21:52:33]:   Creating directory "C:\TeamCity\buildAgent\work\abd984c9980eb3a7\Build\..\bin\artifacts\ILMerge".
[21:52:33]:   C:\TeamCity\buildAgent\work\abd984c9980eb3a7\Build\..\Tools\ILMerge\ILMerge.exe /targetplatform:"v4, %ProgramFiles%\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0" /internalize:C:\TeamCity\buildAgent\work\abd984c9980eb3a7\Build\..\Build\ilmerge.internalize.ignore.txt /target:exe /out:NuPack.exe /log:C:\TeamCity\buildAgent\work\abd984c9980eb3a7\Build\..\bin\artifacts\ILMerge\ilmerge.log /ndebug /allowDup NuPack.exe
[21:52:34]: C:\TeamCity\buildAgent\work\abd984c9980eb3a7\Build\Build.proj(81,9): error MSB3073: The command "C:\TeamCity\buildAgent\work\abd984c9980eb3a7\Build\..\Tools\ILMerge\ILMerge.exe /targetplatform:"v4, %ProgramFiles%\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0" /internalize:C:\TeamCity\buildAgent\work\abd984c9980eb3a7\Build\..\Build\ilmerge.internalize.ignore.txt /target:exe /out:NuPack.exe /log:C:\TeamCity\buildAgent\work\abd984c9980eb3a7\Build\..\bin\artifacts\ILMerge\ilmerge.log /ndebug /allowDup NuPack.exe " exited with code 1.
[21:52:34]: Done Building Project "C:\TeamCity\buildAgent\work\abd984c9980eb3a7\Build\Build.proj" (default targets) -- FAILED.
[21:52:34]: Build FAILED.
[21:52:34]: "C:\TeamCity\buildAgent\work\abd984c9980eb3a7\Build\Build.proj" (default target) (1) ->
[21:52:34]: (ILMergeTheExecutable target) ->
[21:52:34]:   C:\TeamCity\buildAgent\work\abd984c9980eb3a7\Build\Build.proj(81,9): error MSB3073: The command "C:\TeamCity\buildAgent\work\abd984c9980eb3a7\Build\..\Tools\ILMerge\ILMerge.exe /targetplatform:"v4, %ProgramFiles%\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0" /internalize:C:\TeamCity\buildAgent\work\abd984c9980eb3a7\Build\..\Build\ilmerge.internalize.ignore.txt /target:exe /out:NuPack.exe /log:C:\TeamCity\buildAgent\work\abd984c9980eb3a7\Build\..\bin\artifacts\ILMerge\ilmerge.log /ndebug /allowDup NuPack.exe " exited with code 1.
[21:52:34]:     0 Warning(s)
[21:52:34]:     1 Error(s)

Sep 24, 2010 at 5:06 PM
There is a log in something like bin\artifacts\ilmerge - attach that guy and we can look into the details.
____
Rob
"Be passionate in all you do"

http://devlicio.us/blogs/rob_reynolds
http://ferventcoder.com
http://twitter.com/ferventcoder



Developer
Sep 29, 2010 at 5:53 AM

I get this same error when I do a fresh clone and build.

Sep 29, 2010 at 10:29 AM
Looks like the build was broken for one checkin last night but you resolved it.
 
 
On Wed, Sep 29, 2010 at 12:54 AM, dfowler <notifications@codeplex.com> wrote:

From: dfowler

I get this same error when I do a fresh clone and build.

Read the full discussion online.

To add a post to this discussion, reply to this email (nupack@discussions.codeplex.com)

To start a new discussion for this project, email nupack@discussions.codeplex.com

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe or change your settings on codePlex.com.

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at codeplex.com


Developer
Sep 29, 2010 at 10:54 AM

Yea I saw that, not sure how it fixed itself.

Developer
Sep 29, 2010 at 10:54 AM

Btw we need some kind of checkin mailing list.

Sep 29, 2010 at 12:08 PM

Do you want checkins with diff or a build notification/  build failure?

On Sep 29, 2010 5:54 AM, "dfowler" <notifications@codeplex.com> wrote:
> From: dfowler
>
> Btw we need some kind of checkin mailing list.
>
>
Developer
Sep 29, 2010 at 4:13 PM

- Whenever something goes into main, I think it should send email to the checkin alias with the changeset number (and maybe the diff or a link to codeplex with the changeset).
- When the build fails the owner of the checkin should get emails along with some build administratiors (like me or you or anyone who is admin).

Other related things:

We should setup team city so that it uses MSbuild and mstest (not the command line even though that is the easiest). 

Developer
Sep 30, 2010 at 7:00 AM

Can you make me an admin on the build server?

Sep 30, 2010 at 10:07 AM
I can but we are going to move off of this build server once the project goes public.  Do you want team city admin or RDP access?
Developer
Sep 30, 2010 at 4:08 PM

Hmmm, that's true. Just admin access. I just want to know what to change so that we get all the unit test and coverage stuff going.

Oct 1, 2010 at 4:52 AM

so team city does not support the VS code coverage formats out of the box.. but it does support mstest to report unit tests.

Here is the docs on how to enable the test reporting. http://confluence.jetbrains.net/display/TCD5/MSTest+Support

It basically is this:

The build script needs to echo the following message: 

 ##teamcity[importData type='mstest' path='<path to .trx file>']

 TeamCity will then pick up the trx file and it should show unit test output.

Jun 24, 2011 at 9:38 AM

@erichexter: Agent? So you were running this under TFS? Did you do anything else? I'm calling MsBuild from an web Application (ProcessStartInfo) in x86 mode and load user profile. but still the same error.