MSBuild throws 'name too long' on project if called from Jenkins but not CMD

微笑、不失礼 提交于 2020-01-04 06:21:33

问题


If I run the following command manually everything compiles fine.

cd D:\Jenkins\[redacted]\Api>
C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe /property:Configuration=Release Api.sln

If I run the same command (copy/paste) from Jenkins MSBuild gives me the following error for one of my projects

"D:\Jenkins\[Redacted]\Logic\[Redacted].Api2.Logic.csproj" (default target) (26) ->
(GenerateSatelliteAssemblies target) -> 
  ALINK : error AL1061: Cannot set option 'description' because 'The file name is too long. ' 

Why does the MSBuild work when running through the CMD but not via Jenkins? It doesn't look like a permissions issue and only one project out of many that hasn't been touched in months breaks.

Even the error message is a little odd - There is no description in the assemblyinfo and there are much longer file names that compile without issues in the solution.

What could be causing this? The best I could find is this http://connect.microsoft.com/VisualStudio/feedback/details/728795/error-al1061-when-building-satellite-assemblies-with-long-names which was of no use.

来源:https://stackoverflow.com/questions/11317575/msbuild-throws-name-too-long-on-project-if-called-from-jenkins-but-not-cmd

标签
易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!