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

JDK auto install from j.s.c need to be able to specify 32bit/64bit

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major Major
    • core
    • None
    • Platform: All, OS: All

      Currently on a 64bit OS (Linux/Windows/Solaris?) Hudson will favour the 64bit
      JVM if available.

      However for projects that need JNI this can lead to test failures if you only
      create a 32bit library. The only way to do this is then re-package the JDK and
      provide it on a web server for hudson to re-consume (which defeats the purpose
      of the ease of deploying new JVMs.)

      Conversley you might only want to run on a 64bit JDK if you require a large heap.

      Therefore this request is to add a new option to the UI to
      1) force a 64bit JDK (this will then prevent a Java tool being available on
      32bit platforms)
      2) force a 32bit JDK to be installed on 64bit platforms.

      e.g.

      the user can create a JDK "JDK 1.6.0_14 (32bit)" with "force 32bit JDK on 64bit
      hosts=true" and choose that as their java vm for the project and let it run on
      any node. knowing that it will only ever run on a 32bit JDK.

      They could also do the inverse such as choosing a 64bit JDK and then using a
      64bit lable tie the job to a 64bit host.

          [JENKINS-3963] JDK auto install from j.s.c need to be able to specify 32bit/64bit

          Jesse Glick added a comment -

          A reasonable request. UI would probably be a new field in the java.sun.com
          installer labeled "Word Size" or something similar with options

          • Auto (default)
          • 32-bit only
          • 64-bit only

          Jesse Glick added a comment - A reasonable request. UI would probably be a new field in the java.sun.com installer labeled "Word Size" or something similar with options Auto (default) 32-bit only 64-bit only

          I don't see the difference between "auto" and "64bit only". Don't they do the
          same thing?

          Kohsuke Kawaguchi added a comment - I don't see the difference between "auto" and "64bit only". Don't they do the same thing?

          James Nord added a comment -

          from above

          1) force a 64bit JDK (this will then prevent a Java tool being available on
          32bit platforms)

          ie you know if you choose to use jdk1.6.0_14_64 from the UI you will only ever
          build with a 64bit jdk (e.g. for the case where slaves are misconfigured and a
          32bit slave is registered as a 64bit slave)

          James Nord added a comment - from above 1) force a 64bit JDK (this will then prevent a Java tool being available on 32bit platforms) ie you know if you choose to use jdk1.6.0_14_64 from the UI you will only ever build with a 64bit jdk (e.g. for the case where slaves are misconfigured and a 32bit slave is registered as a 64bit slave)

          I have an environment where this would be a boon. We have some jobs that will only work with a 32-bit JDK, though generally we want to use the 64-bit JDKs.

          Bullhorn RelEng added a comment - I have an environment where this would be a boon. We have some jobs that will only work with a 32-bit JDK, though generally we want to use the 64-bit JDKs.

          Ronen Peleg added a comment - - edited

          We still don't have this option, why?

          Ronen Peleg added a comment - - edited We still don't have this option, why?

            Unassigned Unassigned
            teilo James Nord
            Votes:
            9 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated: