Uploaded image for project: 'Bitbucket Server'
  1. Bitbucket Server
  2. BSERV-9070

Ability to set JVM arguments so they are persisted across upgrades

    XMLWordPrintable

Details

    • Suggestion
    • Status: Gathering Interest (View Workflow)
    • Resolution: Unresolved
    • None
    • None
    • None
    • 7
    • 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.

    Description

      In order to increase the memory that Bitbucket Server uses, the admin must edit the setenv.sh script in the application install directory. Unfortunately, that means the settings must be re-applied on each upgrade. Provide a way to change the setting that will be persisted across upgrades.

      Original suggestion:

      It would be nice, if the setenv.sh would first check whether JVM_MINIMUM_MEMORY and JVM_MAXIMUM_MEMORY variables are set and if not, it creates with default values. This would allow to set JVM parameters in the init.d script and would ease the upgrade procedure.

      Workaround
      Set JVM_MINIMUM_MEMORY and JVM_MAXIMUM_MEMORY permanently as environmental variables. This will persist across upgrades without any script modification needed. This is also true for JVM_SUPPORT_RECOMMENDED_ARGS.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              gabor.marosy Gábor Marosy
              Votes:
              10 Vote for this issue
              Watchers:
              14 Start watching this issue

              Dates

                Created:
                Updated: