Details
-
Bug
-
Resolution: Fixed
-
Low
-
None
-
None
Description
There are several things wrong with the bamboo.sh startup script:
1) an option to specify which user to run Bamboo under
2) The startup script takes no care of CWD. Depending on which directory you're in the startup behaves differently.
3) if Bamboo stops abruptly or startup fails, it leaves a bamboo.pid file and this file causes future startup attempts to fail.
4) make use of the JAVA_HOME in bamboo.sh script, Bamboo defaults to the java executable in the System Path - we ask users to set JAVA_HOME, but we never use it in the script
5) Parameterize each of the startup option in RUN_CMD variable or read the options from wrapper.conf file.
Attachments
Issue Links
- is related to
-
BAM-4756 Bamboo wrapper log in <install>/logs/bamboo.log is not rolled
- Closed
-
BAM-2000 bamboo.sh assumes that the correct "java" executable is on the path
- Closed
-
BAM-1934 Externalize all configuration, plugins, and properties fromt the bamboo installation
- Closed
-
BAM-2742 Simplify the Bamboo install process
- Closed
-
BAM-4032 In bamboo.sh *Bamboo.bat JAVA_HOME is not used to start bamboo
- Closed
-
BAM-8045 Wrong BAMBOO_INSTALL directory when bamboo.sh is a symlink
- Closed
- mentioned in
-
Page Loading...