Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-8453

Installer should always use the bundled JRE

XMLWordPrintable

    • 18
    • We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      The installer should always install and use the bundled JRE, even if the server already has an acceptable version of Java installed. This ensures that we run with known-good versions of Java.

      Customers that want to use their own JRE can use the zip distribution.

      Current behaviour

      Bitbucket Server only provides a bundled JRE if Java is not installed or available on the server.
      If Java is already available, the default system Java is used and configured to be used in the service ("Java Virtual Machine:" field in the "Java" tab).

        1. service_not_found.png
          service_not_found.png
          25 kB
        2. upgrade_existing_service.png
          upgrade_existing_service.png
          26 kB

          Form Name

            [BSERV-8453] Installer should always use the bundled JRE

            Svante Gustafsson Björkegren added a comment -

            Hey,
            To add an (in my opinion) important nuance to this Suggestion:
            Per BSERV-9323, as the installing administrator it should be possible to select whether the bundled JRE or a system JRE should be used. I need to be able to have a valid system JRE installed on the server and still have the bundled JRE extracted into the INSTALL-dir

            But then ...
            Using the JAVA_HOME and/or JRE_HOME env variables is then the perfect mechanism to select which JRE to use. This is the way I, as the administrator, am used to manage my Atlassian applications.

            My use case also includes the usage of a configuration management and orchestration tools setup. We have all our Atlassian services managed by e.g. Chef, Puppet etc. and all our Atlassian servers have a common base configuration which is great since it simplifies things a lot. Having Bitbucket to use the zip-distribution if a system JRE needs to be installed will create un-necessary complexity in this area. And re-work of already working setups.

            Cheers,
            // Svante

            Svante Gustafsson Björkegren added a comment - Hey, To add an (in my opinion) important nuance to this Suggestion: Per BSERV-9323 , as the installing administrator it should be possible to select whether the bundled JRE or a system JRE should be used. I need to be able to have a valid system JRE installed on the server and still have the bundled JRE extracted into the INSTALL-dir But then ... Using the JAVA_HOME and/or JRE_HOME env variables is then the perfect mechanism to select which JRE to use. This is the way I, as the administrator, am used to manage my Atlassian applications. My use case also includes the usage of a configuration management and orchestration tools setup. We have all our Atlassian services managed by e.g. Chef, Puppet etc. and all our Atlassian servers have a common base configuration which is great since it simplifies things a lot. Having Bitbucket to use the zip-distribution if a system JRE needs to be installed will create un-necessary complexity in this area. And re-work of already working setups. Cheers, // Svante

            Brent P added a comment -

            tbomfim:

            Can we make sure that we include that change when we upgrade their services?

            Yes. If the user selects "install as a service" any existing service is always overwritten. So, if we implemented this, running the installer would ensure the service would use the bundled JRE (and not any system-installed JRE).

            Brent P added a comment - tbomfim : Can we make sure that we include that change when we upgrade their services? Yes. If the user selects "install as a service" any existing service is always overwritten. So, if we implemented this, running the installer would ensure the service would use the bundled JRE (and not any system-installed JRE).

            Brent P added a comment -

            rbarnes - This isn't a duplicate of that issue. BSERV-7898 wants to use the bundled JRE to run the installer itself (which Juan doesn't think is possible) but this wants to always install the bundled JRE and use it to run Bitbucket (which is possible).

            Brent P added a comment - rbarnes - This isn't a duplicate of that issue. BSERV-7898 wants to use the bundled JRE to run the installer itself (which Juan doesn't think is possible) but this wants to always install the bundled JRE and use it to run Bitbucket (which is possible).

            Roger Barnes (Inactive) added a comment -

            Possible duplicate, can it be rolled into BSERV-7898?

            Roger Barnes (Inactive) added a comment - Possible duplicate, can it be rolled into BSERV-7898 ?

            Brent P added a comment -

            We created this issue off the back of BSERV-8421 - this is our preferred solution to that problem.

            Brent P added a comment - We created this issue off the back of BSERV-8421 - this is our preferred solution to that problem.

              74d6667aa35c Josh Aguilar
              bplump Brent P
              Votes:
              14 Vote for this issue
              Watchers:
              15 Start watching this issue

                Created:
                Updated:
                Resolved: