|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
[JIRA] (JENKINS-15029) Update of MSBuild plugin to 1.15 causes Parameterized trigger plugin to fail.
- [JIRA] (JENKINS-15029) Update of MSBu... [email protected] (JIRA)
- [JIRA] (JENKINS-15029) Update of MSBu... [email protected] (JIRA)
- [JIRA] (JENKINS-15029) Update of MSBu... [email protected] (JIRA)
- [JIRA] (JENKINS-15029) Update of MSBu... [email protected] (JIRA)
- [JIRA] (JENKINS-15029) Update of MSBu... [email protected] (JIRA)
- [JIRA] (JENKINS-15029) Update of MSBu... [email protected] (JIRA)
- [JIRA] (JENKINS-15029) Update of MSBu... [email protected] (JIRA)
- [JIRA] (JENKINS-15029) Update of MSBu... [email protected] (JIRA)
- [JIRA] (JENKINS-15029) Update of MSBu... [email protected] (JIRA)
- [JIRA] (JENKINS-15029) Update of MSBu... [email protected] (JIRA)
- [JIRA] (JENKINS-15029) Update of MSBu... [email protected] (JIRA)
- [JIRA] (JENKINS-15029) Update of MSBu... [email protected] (JIRA)
- [JIRA] (JENKINS-15029) Update of MSBu... [email protected] (JIRA)

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