[
https://issues.jenkins-ci.org/browse/JENKINS-13863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163601#comment-163601
]
Aaron Laws commented on JENKINS-13863:
--------------------------------------
There we go! Just change the documentation to make the implementation correct!
Although the documentation is still probably lacking a bit. Perhaps
{panel:title=| borderStyle = dashed}This is the absolute path to the project
file MSBuild will use. Alternatively, if the project file is in the root
directory of the project's workspace, simply the name of the project file will
suffice.{panel}
Can someone give me directions on compiling the {{MSBuild Plugin}} and testing
it locally? I would be happy to give this a whack. It seems like it should be
simple. Most frameworks can resolve relative paths.
> MSBuild is unable to build projects in a different directory
> ------------------------------------------------------------
>
> Key: JENKINS-13863
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13863
> Project: Jenkins
> Issue Type: Bug
> Components: msbuild
> Affects Versions: current
> Environment: MS Windows Server 2008
> Reporter: Aaron Laws
> Assignee: kdsweeney
> Priority: Minor
> Labels: path, plugin
> Attachments: badbuild.txt, badconfig.PNG, betterbuild.txt,
> goodbuild.txt, goodconfig.PNG
>
>
> I use SVN to checkout a project to {{.\proj\}} and a dependency to
> {{.\dep\}}. The {{.sln}} file is at {{.\proj\proj.sln}}. I us the MsBuild
> plugin with the setting "MsBuild Build File" = "{{proj\proj.sln}}" (or a
> number of variants such as {{.\proj\proj.sln}}). Msbuild fails with
> {{MSB1009: Project file does not exist.}} However, running a similar command
> manually succeeds.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
