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

Call microsoft batch trigger "\Java\jre1.8.0_141\bin" was unexpected

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Trivial
    • Resolution: Not A Defect
    • Component/s: _unsorted
    • Environment:
      Jenkins ver. 2.73.1 with
      java-8-openjdk-amd64
      java.runtime.version 1.8.0_131-8u131-b11-2ubuntu1.16.04.3-b11

      Microsoft Windows Server 2012 R2 with:
      java version 1.8.0_241
    • Similar Issues:

      Description

      TheI use Jenkins for compilations with CMake and Visual Studio. Recently we upgrade Visual Studio Compiler to 2017 to support C++17.

      Before this upgrade to can run CMake, we use a Microsoft .bat to initilialize compiler environement. Now that we have upgrade our Microsoft Compiler, we tried to do the same with the following command in a pipeline "bat script:" step:

      call "C:\\Program Files (x86)\\Microsoft Visual Studio\\2017\\Enterprise\\VC\\Auxiliary\\Build\\vcvars64.bat

      And the following output appears: 

      D:\JENKINS\workspace\Tests\msvc_test\build>call "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Auxiliary\Build\vcvars64.bat" 
      \Java\jre1.8.0_141\bin"" ‚tait inattendu.
      Build step 'Exécuter une ligne de commande batch Windows' marked build as failure
      Finished: FAILURE
      

      The previous .batch works perfectly

      Is there something that I can attempt ? I've upgrade my jenkins, all plugins but nothing changes. This problem is the same even I use pipeline or not (freestyle projects...)

        Attachments

          Activity

          Hide
          oleg_nenashev Oleg Nenashev added a comment -

          Does not seem like a Jenkins defect.
          Estrada Matthieu is it still actual?

          Show
          oleg_nenashev Oleg Nenashev added a comment - Does not seem like a Jenkins defect. Estrada Matthieu is it still actual?
          Hide
          algorys Estrada Matthieu added a comment - - edited

          Oleg Nenashev Yes I've solved this problem by using:

          bat '''
              call "C:\\Program Files (x86)\\Microsoft Visual Studio\\2017\\Professional\\VC\\Auxiliary\\Build\\vcvars64.bat"
              ...
          '''
          
          Show
          algorys Estrada Matthieu added a comment - - edited Oleg Nenashev Yes I've solved this problem by using: bat ''' call "C:\\Program Files (x86)\\Microsoft Visual Studio\\2017\\Professional\\VC\\Auxiliary\\Build\\vcvars64.bat" ... '''
          Hide
          oleg_nenashev Oleg Nenashev added a comment -

          Not a defect then. The installation path has changed from Enterprise to Professional die to the change of Visual Studio version. There is nothing we can do on the Jenkins project side

          Show
          oleg_nenashev Oleg Nenashev added a comment - Not a defect then. The installation path has changed from Enterprise to Professional die to the change of Visual Studio version. There is nothing we can do on the Jenkins project side

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            algorys Estrada Matthieu
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: