In order to enable the support of JDK11 for Jenkins and its plugins, the Jenkinsfile of plugins should be completed allowing to build and test the plugin using JDK11 as well as JDK8.

      The configuration we propose to apply is the following:

       

      buildPlugin(configurations: [  [platform: 'linux', jdk: '8'],  [platform: 'linux', jdk: '11'],  [platform: 'windows', jdk: '11'], ])

       

      The goal is to allow building and testing over JDK11 for both Windows & Linux.

      Building and testing over JDK8 will still be kept for Linux.

      We also propose to keep only one Windows flavor in order to save infrastructure costs, hence having only JDK11 for Windows.

          [JENKINS-66887] Enable JDK11 in plugins' Jenkinsfile

          Antoine Neveux created issue -
          Antoine Neveux made changes -
          Component/s New: git-client-plugin [ 17423 ]
          Description Original: In order to enable the support of JDK11 for Jenkins and its plugins, the Jenkinsfile of the git-plugin should be completed allowing to build and test the plugin using JDK11 as well as JDK8. New: In order to enable the support of JDK11 for Jenkins and its plugins, the Jenkinsfile of the git-*plugin should be completed allowing to build and test the plugin using JDK11 as well as JDK8.
          Summary Original: Enable JDK11 in git-plugin Jenkinsfile New: Enable JDK11 in git-(*)plugin Jenkinsfile
          Antoine Neveux made changes -
          Summary Original: Enable JDK11 in git-(*)plugin Jenkinsfile New: Enable JDK11 in plugins' Jenkinsfile
          Antoine Neveux made changes -
          Description Original: In order to enable the support of JDK11 for Jenkins and its plugins, the Jenkinsfile of the git-*plugin should be completed allowing to build and test the plugin using JDK11 as well as JDK8. New: In order to enable the support of JDK11 for Jenkins and its plugins, the Jenkinsfile of plugins should be completed allowing to build and test the plugin using JDK11 as well as JDK8.

          The configuration we propose to apply is the following:

          {{{{}}}}
          {code:java}
          buildPlugin(configurations: [ [platform: 'linux', jdk: '8'], [platform: 'linux', jdk: '11'], [platform: 'windows', jdk: '11'], ]){code}
          {{{{}}}}

          The goal is to allow building and testing over JDK11 for both Windows & Linux.

          Building and testing over JDK8 will still be kept for Linux.

          We also propose to keep only one Windows flavor in order to save infrastructure costs, hence having only JDK11 for Windows.
          Antoine Neveux made changes -
          Description Original: In order to enable the support of JDK11 for Jenkins and its plugins, the Jenkinsfile of plugins should be completed allowing to build and test the plugin using JDK11 as well as JDK8.

          The configuration we propose to apply is the following:

          {{{{}}}}
          {code:java}
          buildPlugin(configurations: [ [platform: 'linux', jdk: '8'], [platform: 'linux', jdk: '11'], [platform: 'windows', jdk: '11'], ]){code}
          {{{{}}}}

          The goal is to allow building and testing over JDK11 for both Windows & Linux.

          Building and testing over JDK8 will still be kept for Linux.

          We also propose to keep only one Windows flavor in order to save infrastructure costs, hence having only JDK11 for Windows.
          New: In order to enable the support of JDK11 for Jenkins and its plugins, the Jenkinsfile of plugins should be completed allowing to build and test the plugin using JDK11 as well as JDK8.

          The configuration we propose to apply is the following:

           
          {code:java}
          buildPlugin(configurations: [ [platform: 'linux', jdk: '8'], [platform: 'linux', jdk: '11'], [platform: 'windows', jdk: '11'], ]){code}
           

          The goal is to allow building and testing over JDK11 for both Windows & Linux.

          Building and testing over JDK8 will still be kept for Linux.

          We also propose to keep only one Windows flavor in order to save infrastructure costs, hence having only JDK11 for Windows.
          Mark Waite made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]

            markewaite Mark Waite
            aneveux Antoine Neveux
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: