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

No msbuild section in configuration or global tools after install

    • Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Blocker Blocker
    • msbuild-plugin
    • None
    • Jenkins 2.10 and msbuild plugin 1.25

      I have installed latest version but i cant set the path for msbuild.exe in configuration

        1. 2.JPG
          2.JPG
          59 kB
        2. 1.JPG
          1.JPG
          109 kB

          [JENKINS-36138] No msbuild section in configuration or global tools after install

          Govendhan Chandrasekar created issue -

          Hello,

          Could you please retry with msbuild-plugin 1.26 ?

          Thanks

          Lionel Cabasson added a comment - Hello, Could you please retry with msbuild-plugin 1.26 ? Thanks
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 172793 ] New: JNJira + In-Review [ 184781 ]

          Sahyun Kim added a comment -

          Same error...

          Sahyun Kim added a comment - Same error...

          Also do not see this on a Mac Mini fresh jenkins install on version 1.26

          Antonio Guglielmo added a comment - Also do not see this on a Mac Mini fresh jenkins install on version 1.26

          I recommend combining this report with JENKINS-34577 since the details seems to indicate the same behavior

          Antonio Guglielmo added a comment - I recommend combining this report with JENKINS-34577 since the details seems to indicate the same behavior

          Rolled Jenkins Back to 1.651.3 and can now see the admin configuration at a global level. Seems to be a version mismatch in some config / and or the missing global.jelly that I can see some other plugins that are working successfully. Its a issue with the jenkins version, not the plugin specifically but should be enhanced to support the new versions of jenkins.

          Antonio Guglielmo added a comment - Rolled Jenkins Back to 1.651.3 and can now see the admin configuration at a global level. Seems to be a version mismatch in some config / and or the missing global.jelly that I can see some other plugins that are working successfully. Its a issue with the jenkins version, not the plugin specifically but should be enhanced to support the new versions of jenkins.
          Lionel Cabasson made changes -
          Link New: This issue is duplicated by JENKINS-34577 [ JENKINS-34577 ]

          agciber Thanks for your feedback, I may try to investigate this matter when I can find some time.

          Lionel Cabasson added a comment - agciber Thanks for your feedback, I may try to investigate this matter when I can find some time.
          Lionel Cabasson made changes -
          Attachment New: 1.JPG [ 33488 ]
          Attachment New: 2.JPG [ 33489 ]

            marshall777 Lionel Cabasson
            govendhan Govendhan Chandrasekar
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: