Continuous Integration times out when building VSIX project01 Jan 2016
Recently our AppVeyor builds started to intermittently fail with message Build execution time has reached the maximum allowed time for your plan (60 minutes). We fixed it with a one line change to the .csproj
If the CI build succeeds and all tests pass, yet the process times out, check the CI console for the following line:
Setting up Visual Studio for debugging extensions. This one-time operation may take a minute or more.
This operation takes over half an hour in our setup and eventually times out the CI build. We fixed this issue by preventing VSIX deployment to Visual Studio during CI builds.
Solution: conditionally prevent deploying the extension
To prevent deploying the extension in AppVeyor builds, use the following element in your Visual Studio Extension (VSIX) project’s .csproj file:
<DeployExtension Condition="'$(AppVeyor)' != ''">False</DeployExtension>
In the extension’s .csproj find all instances of
<DeployExtension>True</DeployExtension> and modify them to match the code above.
The .csproj may not have the element
DeployExtension since it defaults to
True. In this case, you should add this element either to the first
<PropertyGroup> or to one of configuration-specific property groups like
<PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug|AnyCPU' ">
We added it to the first
Credit for this solution goes to latkin’s PR to the Microsoft/visualfsharp repo.
You might have also noticed many compilation messages at the very bottom of the log that mentiont
PNPDTest. I’m not sure if they’re related to the issue (they could be the reason of the delay), but scrolling up above them will reveal the
Setting up Visual Studio for debugging extensions line.
DEVENV : warning : Test name: PNPDTest::PNPCancelStopDevice - Unique property value already defined. This value will be overwritten and may cause unexpected behaviors. Property: Kits.Description. Old value: This test exercises various Plug and Play (PnP)-related code paths in the driver and user-mode components.. New Value: This test uses SetupDi API to send DIF_REMOVE request for the installers to process remove.. Current property level: Test.