VisualGDB running as TFS remote build failure

Sysprogs forums Forums VisualGDB VisualGDB running as TFS remote build failure

This topic contains 9 replies, has 2 voices, and was last updated by  support 2 months ago.

Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • #24254

    terry_short29
    Participant

    I tried to set up a remote build on our TFS build agent and I think I had it working before but now it fails every time with the following message.

    Are there some build variables I can set to fix this?

    • This topic was modified 2 months, 1 week ago by  support. Reason: formatting
    #24256

    support
    Keymaster

    Hi,

    This looks like a bug that was fixed in the latest v5.4 release. Please try updating to it.

    #24281

    terry_short29
    Participant

    Changed the error, now get…

    2019-03-15T08:35:59.8663061Z Build started 15/03/2019 08:35:59.
    2019-03-15T08:36:00.5850640Z 1>Project “C:\BuildAgentV2\_work\31\s\TDS07KB.sln” on node 1 (default targets).
    2019-03-15T08:36:00.5850640Z 1>ValidateSolutionConfiguration:
    2019-03-15T08:36:00.5850640Z Building solution configuration “Release|VisualGDB”.
    2019-03-15T08:36:01.6944518Z 1>Project “C:\BuildAgentV2\_work\31\s\TDS07KB.sln” (1) is building “C:\BuildAgentV2\_work\31\s\TDS07KB.vcxproj” (2) on node 1 (default targets).
    2019-03-15T08:36:01.6944518Z 2>PrepareFastUpToDataCheckDatabase:
    2019-03-15T08:36:01.6944518Z VisualGDB version 5.4.103.3000
    2019-03-15T08:36:01.6944518Z System.ArgumentException
    2019-03-15T08:36:01.6944518Z System.ArgumentException: Path cannot be the empty string or all whitespace.
    2019-03-15T08:36:01.6944518Z at System.IO.Directory.CreateDirectory(String path)
    2019-03-15T08:36:01.6944518Z at Sysprogs.Build.Tasks.InitializeFastUpToDateCheckFile.Execute()
    2019-03-15T08:36:01.7569552Z ##[error]C:\Program Files (x86)\Sysprogs\VisualGDB\MSBuild\Targets\FastUpToDateCheck.targets(5,2): Error : Path cannot be the empty string or all whitespace.
    2019-03-15T08:36:01.7569552Z 2>C:\Program Files (x86)\Sysprogs\VisualGDB\MSBuild\Targets\FastUpToDateCheck.targets(5,2): error : Path cannot be the empty string or all whitespace. [C:\BuildAgentV2\_work\31\s\TDS07KB.vcxproj]
    2019-03-15T08:36:01.7569552Z 2>Done Building Project “C:\BuildAgentV2\_work\31\s\TDS07KB.vcxproj” (default targets) — FAILED.
    2019-03-15T08:36:01.7569552Z 1>Done Building Project “C:\BuildAgentV2\_work\31\s\TDS07KB.sln” (default targets) — FAILED.
    2019-03-15T08:36:01.7569552Z
    2019-03-15T08:36:01.7569552Z Build FAILED.

    #24284

    support
    Keymaster

    This looks like you have updated the VisualGDB binaries, but might be still using the MSBuild targets files from the old version. Please double-check that the project builds with VisualGDB 5.4 from Visual Studio and that the SysprogsPlatform.targets and other MSBuild files on the TFS machine match the corresponding files on the machine where the build succeeds.

    #24313

    terry_short29
    Participant

    I tried running the build from within VS on the remote build machine succeeded. Building with V5.4 on my development machine worked. What else can I check? Can I turn up some debugging or something?

    #24338

    support
    Keymaster

    Yes, please try running msbuild with the -verbosity:diag switch and either attach the diagnostic log here, or send it via our support form. It should explain what is going on.

    #24342

    terry_short29
    Participant

    Build log as requested…

    Attachments:
    You must be logged in to view attached files.
    #24387

    support
    Keymaster

    Thanks, looks like your project did not have the $(IntDir) variable set and that triggered an unexpected path format inside VisualGDB. We have added a check for it in the following build: VisualGDB-5.4.103.3019.msi

    #24390

    terry_short29
    Participant

    I checked and the project does have IntDir set on my development PC however, I tried it with your new version and it seems to build ok now.

    #24399

    support
    Keymaster

    No problem. The IntDir might have been set in a different order then (i.e. before VisualGDB computes the paths of some intermediate files). Either way, we have added the checks for this case in the new build, so unless you encounter further problems, the project should be good to go.

Viewing 10 posts - 1 through 10 (of 10 total)

You must be logged in to reply to this topic.