-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Low
-
None
-
Affects Version/s: 9.4.0, 10.0.0, 10.1.0, 10.2.0, 10.3.0, 10.4.0
-
Component/s: Documentation (User)
-
None
-
2
-
Severity 3 - Minor
-
4
Issue Summary
The Console and unattended mode section in the Run the Bitbucket installer documentation is missing the following response-file parameters implemented in the Bitbucket installer:
- confirm.disable.plugins$Boolean
- container.configuration.ignore$Boolean
They're mandatory acknowledgements when their respective upgrade checks are triggered.
An unattended upgrade can therefore exit if they're not set.
Steps to Reproduce
- Prepare a test Bitbucket instance with at least one user-installed app. that will be upgraded to a later major version.
- Use the Run the Bitbucket installer doc and follow the Console and unattended mode instructions.
- Perform a major version upgrade.
For example, if the current Bitbucket version is 9.x, upgrade and use an installer for 10.x
./atlassian-bitbucket-10.x.x-x64.bin -q -varfile /absolute/path/response.varfile - Observe that installation exits with instructions to add:
confirm.disable.plugins$Boolean=true
This parameter is not documented.
Additional reproduction for container.configuration.ignore$Boolean:
Repeat with a customized legacy server.xml in the Bitbucket home dir.
Omit the container acknowledgement.
The installer exits requesting container.configuration.ignore$Boolean=true, which is also undocumented.
Expected Results
Include the two conditional acknowledgements in the Run the Bitbucket installer documentation.
Suggested content:
| Parameters | Accepted values | Description |
|---|---|---|
| confirm.disable.plugins$Boolean | true false |
Acknowledges that user-installed apps will be disabled. Required to be set to true for unattended major version upgrades when user-installed .jar app files are detected. Check app compatibility, update where necessary, and re-enable apps after upgrading. |
| container.configuration.ignore$Boolean | true false |
Acknowledges that customized legacy server.xml configuration will be ignored after upgrading. Must be set to true for unattended upgrades when such configuration is detected. The installer checks <BITBUCKET_HOME>/server.xml, or <BITBUCKET_HOME>/shared/server.xml if the first file does not exist, and compares its MD5 checksum with the known default. Required customizations in the server.xml file should be migrated to bitbucket.properties before proceeding. |
Actual Results
The current table lists general response file parameters but omits the two conditional acknowledgements.
Workaround
Add the omitted parameters to the response.varfile.