Sysprogs forums › Forums › VisualGDB › No toolchain found on Jenkins Build
- This topic has 1 reply, 2 voices, and was last updated 1 hour, 17 minutes ago by
support.
-
AuthorPosts
-
February 2, 2026 at 00:34 #37091
Roman.Thiel
ParticipantHi,
we have a problem with a new jenkins server. I setup the latest jenkins with latest VGDB and VS2022. The build fails with:
C:\Program Files (x86)\Sysprogs\VisualGDB\MSBuild\SysprogsPlatform.targets(98,2): error : No toolchain found. Please configure the toolchain via VisualGDB Project Properties.
When I connect to the server via remote desktop, I can open the solution and build it. No Problem. I have installed and tested different toolchains, but still not building.
Any Idea?
Bests regards,
Roman
Here the log:
Path To MSBuild.exe: msbuild.exe
Executing the command cmd.exe /C ” chcp 65001 & msbuild.exe /p:Configuration=Debug TestProject.sln ” && exit %%ERRORLEVEL%% from C:\ProgramData\Jenkins\.jenkins\workspace\LiveTest
[LiveTest] $ cmd.exe /C ” chcp 65001 & msbuild.exe /p:Configuration=Debug TestProject.sln ” && exit %%ERRORLEVEL%%
Aktive Codepage: 65001.
MSBuild-Version 17.14.23+b0019275e für .NET Framework
Der Buildvorgang wurde am 29.01.2026 16:37:33 gestartet.Projekt “C:\ProgramData\Jenkins\.jenkins\workspace\LiveTest\TestProject.sln” auf Knoten “1” (Standardziele).
ValidateSolutionConfiguration:
Die Projektmappenkonfiguration “Debug|VisualGDB” wird erstellt.
Das Projekt “C:\ProgramData\Jenkins\.jenkins\workspace\LiveTest\TestProject.sln” (1) erstellt “C:\ProgramData\Jenkins\.jenkins\workspace\LiveTest\TestProject\TestProject.vcxproj” (2) auf Knoten “1” (Standardziele).
C:\Program Files (x86)\Sysprogs\VisualGDB\MSBuild\SysprogsPlatform.targets(98,2): error : No toolchain found. Please configure the toolchain via VisualGDB Project Properties. [C:\ProgramData\Jenkins\.jenkins\workspace\LiveTest\TestProject\TestProject.vcxproj]
Die Erstellung des Projekts “C:\ProgramData\Jenkins\.jenkins\workspace\LiveTest\TestProject\TestProject.vcxproj” ist abgeschlossen (Standardziele) — FEHLER.
Die Erstellung des Projekts “C:\ProgramData\Jenkins\.jenkins\workspace\LiveTest\TestProject.sln” ist abgeschlossen (Standardziele) — FEHLER.Fehler beim Buildvorgang.
“C:\ProgramData\Jenkins\.jenkins\workspace\LiveTest\TestProject.sln” (Standardziel) (1) ->
“C:\ProgramData\Jenkins\.jenkins\workspace\LiveTest\TestProject\TestProject.vcxproj” (Standardziel) (2) ->
(CheckSettings Ziel) ->
C:\Program Files (x86)\Sysprogs\VisualGDB\MSBuild\SysprogsPlatform.targets(98,2): error : No toolchain found. Please configure the toolchain via VisualGDB Project Properties. [C:\ProgramData\Jenkins\.jenkins\workspace\LiveTest\TestProject\TestProject.vcxproj]0 Warnung(en)
1 FehlerVerstrichene Zeit 00:00:00.05
Build step ‘Ein Visual Studio-Projekt oder eine Lösung mit MSBuild bauen’ marked build as failure
Finished: FAILUREFebruary 2, 2026 at 12:50 #37094support
KeymasterHi,
This is to be expected. VisualGDB manages toolchains and BSPs by generating %LOCALAPPDATA%\VisualGDB\FindXXX.props files that have a structure like this:
- If (ID = ‘xxx’ and VERSION = ‘yyy’)
- Include <toolchain-specific .props file>
- If (…)
If you are running MSBuild from a different user account, the files will not be present in %LOCALAPPDATA%, and MSBuild will not load the correct toolchain properties.
The easiest workaround would be to simply run the Jenkins task from the same user account (in Jenkins parameters, or using runas). This will automatically pull toolchains, BSPs, licensing information, etc.
If you absolutely have to use another account, you would need to manually copy the .props files (and possibly, other files like the test frameworks). These files are located under %LOCALAPPDATA%\VisualGDB, so copying the entire directory could be a good starting point.
You can also configure VisualGDB to generate batch files for unattended building as shown here. This way, the projects can be built in the test environment without having to install VisualGDB there.
- If (ID = ‘xxx’ and VERSION = ‘yyy’)
-
AuthorPosts
- You must be logged in to reply to this topic.