Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-9643

MSBuild plugin fails to build scripts with arbitrary filename extensions



    • Bug
    • Status: Resolved (View Workflow)
    • Major
    • Resolution: Fixed
    • msbuild-plugin
    • None
    • Win 7


      One of the latest updates – 1.5 or maybe 1.4 – has broken a number of my builds.

      I use the MSBuild plugin to build msbuild scripts named "[foo].msbuild". These scripts do a number of pre and post-build actions.

      The plugin seems to not recognise the script file and I get a build failure along the lines of "Could not find .proj or .sln file". In other cases, I think when the [foo] in foo.msbuild matches foo.sln, the solution file is built directly. This is no good as the prebuild actions aren't done.

      One workaround I have found is to put an optional argument into the appropriate textbox, e.g. "/v:d" which turns on Debug verbosity.

      I would like to be able to call any filename from the MSBuild plugin, as I would when using MSBuild.exe directly on the command line.


        Issue Links


            cjbrew chris yate created issue -
            ngraziano Nicolas Graziano made changes -
            Field Original Value New Value
            Link This issue is duplicated by JENKINS-9645 [ JENKINS-9645 ]
            gbois Gregory Boissinot made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            gbois Gregory Boissinot made changes -
            Assignee kdsweeney [ kdsweeney ] gbois [ gbois ]
            gbois Gregory Boissinot made changes -
            Resolution Fixed [ 1 ]
            Status In Progress [ 3 ] Resolved [ 5 ]
            rtyler R. Tyler Croy made changes -
            Workflow JNJira [ 139817 ] JNJira + In-Review [ 188698 ]


              gbois Gregory Boissinot
              cjbrew chris yate
              0 Vote for this issue
              0 Start watching this issue