Patch provided in BAM-15732.

FWIW, we recently open-sourced our bamboo_agent Puppet module, which generates an init script for bamboo agents. It can also set capabilities, and properties in wrapper.conf. http://forge.puppetlabs.com/kayak/bamboo_agent

Hi Jon,

Given there is no RPM, what are the best practices for automated installation and uninstallation on a RHEL system? Either in kickstart (anaconda) or a post build configuration management system like CFengine, Puppet or Chef?

Puppet is what many of our customers and what we use internally at Atlassian use to manage Bamboo servers and agents.

You might be interested in using this puppet module to manage your Bamboo server. We've got an issue open to document and formalise the use of puppet for Bamboo installations but as it stands it is currently unsupported by Atlassian. You should watch and vote for that ticket to be notified of when it is officially supported.

pleschev leads the team that maintains our internal Bamboo instances. Peter, are we able to share the puppet module we use for managing our agents internally or is it too tied up with our internal infrastructure?

Thanks
James

Jon,

We have an active community of developers in our ecosystem, who offer help via Answers, or via paid services through our experts.

Cheers,
Armen

Given there is no RPM, what are the best practices for automated installation and uninstallation on a RHEL system? Either in kickstart (anaconda) or a post build configuration management system like CFengine, Puppet or Chef?

Currently the product as supplied comes with a startup script that does not work as a RHEL init script. The PID file support is non standard and does not work with the system toolset including service(8) & chkconfig(8). Further the script does not source the function library at /etc/init.d/functions which provides support for proper PID file locking and other common requirements for a RHEL init script. As well, the script is written such that the CWD must be the same as the Bamboo Java HOME directory in order for it to work. A proper RHEL init script would initialize the Java HOME directory and additional variables through a file in /etc/sysconfig. What are the recommended best practices for automated start, stop, restart and status inquiry?

If such support is not available through Atlassian, is there a contributing (/contrib) community of users that has solved these fundamental concerns?

thankYouInAdvance for your kind consideration of these matters of important matters.