![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
kdsweeney
|
|
Attachments:
|
msbuildInvalid.PNG, msbuildValid.PNG, mstestInvalid.PNG, mstestValid.PNG |
|
Components:
|
msbuild-plugin, mstest-plugin |
|
Created:
|
02/Mar/15 3:20 AM
|
|
Description:
|
When modifying the Jenkins configuration the validators that run to check if the value you typed in exists evaluate to invalid when you specify an executable instead of the directory it resides in. If you only specify the directory to appease the validator, the plugin does not work as it seems to expect a path all the way down to the .exe.
I've noticed this on both mstest and msbuild plugins, but it may affect the configuration of others as well.
I am attaching screenshots of the configuration page to show the "valid"(doesn't work) and the "invalid"(does work) state of the page.
When only specifying the directory, the resulting command for msbuild is this:
Executing the command cmd.exe /C " C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ /p:VisualStudioVersion=12.0 /t:build /p:Configuration=Release
'C:\Windows\Microsoft.NET\Framework64\v4.0.30319\' is not recognized as an internal or external command, operable program or batch file.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
Bobby Dineen
|
|
|
|
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
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/d/optout.
