-
Bug
-
Resolution: Cannot Reproduce
-
Minor
-
Windows Server 2008, Java 1.6.0_43, Jenkins 1.517, Coverity Plugin 1.2.3, MSBuild Plugin 1.16
Coverity works with MSBuild only when the user creates their own MSBuild script via a "Execute Windows batch command" build step and executes the following command:
[Builds] $ C:\Coverity\CIC\static-analysis\bin\cov-build --dir C:\CoverityAnalyzeDir cmd /c call C:\Temp\hudson56334.bat
However, if someone attempts to run Coverity with the MSBuild plugin which has environment variables in it, the following command gets executed and an error occurs:
[JENKINS_COVERITY_TEST] $ C:\Coverity\CIC\static-analysis\bin\cov-build --dir C:\CoverityAnalyzeDir cmd.exe /C C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe /t:Clean;Build /nologo /p:Configuration=Release %BUILD_DIRECTORY%\Project.sln && EXIT %%ERRORLEVEL%%
The filename, directory name, or volume label syntax is incorrect.
- depends on
-
JENKINS-14833 Jenkins variables are not expanded in Coverity plugin
- Closed