Details
-
Bug
-
Status: Resolved (View Workflow)
-
Major
-
Resolution: Incomplete
-
None
Description
Upgraded Jenkins MSBuild plugin to 1.15 and Parameterized trigger plugin stops passing variables to MSBuild. This causes our builds to fails as paths aren't resolved.
When I revert MSBuild back to 1.12 the correct variables are resolved.
This is an extract from the console log:
FailedConsole Output
Started by upstream project "TFS Get - MiX Central - Main" build number 917
Building in workspace C:\Software\Jenkins\.jenkins\jobs\MiX Track Web - Build\workspace
No emails were triggered.
Path To MSBuild.exe: C:\WINDOWS\Microsoft.NET\Framework64\v4.0.30319\MSBuild.exe
FATAL: Can't find %SOURCE%\MiX.AssetManagement\MiX.AssetManagement.Reports.Web\MiX.AssetManagement.Reports.Web.csproj file
Build step 'Build a Visual Studio project or solution using MSBuild' changed build result to FAILURE
Build step 'Build a Visual Studio project or solution using MSBuild' marked build as failure
Email was triggered for: Failure
Sending email for trigger: Failure
Sending email to: kolie.vanstaden@mixtelematics.com stephan.visagie@mixtelematics.com michaelc@mixtel.com
Finished: FAILURE
Attachments
Activity
Gregory Boissinot
added a comment - For summary, it doesn't work for only Windows Server 2003? 
Michael Chamberlain
added a comment - Hello Gregory
Unfortunately I don't have any time to test exactly what the problem could be.(It could even be environmental setting) It just seemed strange that it worked fine on Windows Server 2008 and not 2003.
It's no longer an issue for me as there is a workaround by using the UNIX format to reference the parameter.
Best regards
Michael
Michael Chamberlain
added a comment - Hello Gregory
Unfortunately I don't have any time to test exactly what the problem could be.(It could even be environmental setting) It just seemed strange that it worked fine on Windows Server 2008 and not 2003.
It's no longer an issue for me as there is a workaround by using the UNIX format to reference the parameter.
Best regards
Michael 
ikedam
added a comment - Sounds not related with parameterized-trigger plugin.
Points that may help:
- What happens without parameterized-trigger? (triggering directly)
- What happens changing SOURCE to other name? (it may be a reserved name)
- What is output when run set with Windows batch builder? (SOURCE is logged?)
- Attach build.xml of failed build with msbuild-plugin.
ikedam
added a comment - Sounds not related with parameterized-trigger plugin.
Points that may help:
What happens without parameterized-trigger? (triggering directly)
What happens changing SOURCE to other name? (it may be a reserved name)
What is output when run set with Windows batch builder? (SOURCE is logged?)
Attach build.xml of failed build with msbuild-plugin.
Gregory Boissinot
added a comment - Mark it as incomplete for now 
Hello Gregory.
I've noticed that in our production environment I didn't have any problems with the %source% parameter on our 'Windows Server 2008 R2' computers.
I DID have the problem on our 'Windows Server 2003' computers though. Both tests where done with the last version (MSBuild v1.16).
Using a job to pass %SOURCE% parameter to another job. So in the end, on my Windows Server 2003 computers I had to change all the %SOURCE% parameters in my MSBUILD lines to ${SOURCE} for the parameter to pass in correctly to MSBUILD.
Regards