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

JDK selection is hidden even when a JDK is configured

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • core
    • None

      "default" JDK is the one present in user PATH - let's say JDK6
      if I want to use an alternative JDK5, I declare it on system configuration
      But I still can't edit my project configuration to select JDK and it still run with JDK6
      I need to declare a 2nd JDK so that the select box appears and I can configure my JDK5 build.

      I suggest to deprecate support for "Default" JDK, as this is confusing and dependent on host system configuration.

      To ensure backward compatibility, jenkins could detect at startup jobs that don't have a <JDK> element in config and automatically create a "System" JDK in global configuration based on System.getProperty('java.home').

        1. config.no.jdk.xml
          4 kB
        2. config.with.jdk.xml
          4 kB

          [JENKINS-10191] JDK selection is hidden even when a JDK is configured

          Nicolas De Loof created issue -
          Nicolas De Loof made changes -
          Description Original: "default" JDK is the one present in user PATH - let's say JDK6
          if I want to use an alternative JDK5, I declare i on system configuration
          But I still can't edit my project configuration to select it
          I need to declare a 2nd JDK so that the select box appears and I can configure my JDK5 build.

          I suggest to deprecate support for "Default" JDK.

          To ensure backward compatibility, jenkins can detect at startup jobs that don't have a <JDK> element in config and automatically create a "System" JDK in global configuration based on 'java.home'.
          		New: "default" JDK is the one present in user PATH - let's say JDK6
          if I want to use an alternative JDK5, I declare it on system configuration
          But I still can't edit my project configuration to select JDK and it still run with JDK6
          I need to declare a 2nd JDK so that the select box appears and I can configure my JDK5 build.

          I suggest to deprecate support for "Default" JDK, as this is confusing and dependent on host system configuration.

          To ensure backward compatibility, jenkins could detect at startup jobs that don't have a <JDK> element in config and automatically create a "System" JDK in global configuration based on System.getProperty('java.home').
          Nicolas De Loof made changes -
          Link New: This issue is related to JENKINS-755 [ JENKINS-755 ]
          Andreas Horst made changes -
          Link New: This issue is related to JENKINS-12550 [ JENKINS-12550 ]
          Andreas Horst made changes -
          Attachment New: config.no.jdk.xml [ 26415 ]
          Attachment New: config.with.jdk.xml [ 26416 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 140379 ] New: JNJira + In-Review [ 175262 ]
          Daniel Beck made changes -
          Link New: This issue is duplicated by JENKINS-38911 [ JENKINS-38911 ]
          Isa Vilacides made changes -
          Labels New: java11 java11-compatibility
          Isa Vilacides made changes -
          Labels Original: java11 java11-compatibility New: java11 java11-compatibility triaged
          Tim Jacomb made changes -
          Labels Original: java11 java11-compatibility triaged
          Tim Jacomb made changes -
          Priority Original: Major [ 3 ] New: Minor [ 4 ]

            Unassigned Unassigned
            ndeloof Nicolas De Loof
            Votes:
            11 Vote for this issue
            Watchers:
            13 Start watching this issue

              Created:
              Updated: