matisku/bamboo-docker

Bamboo Docker Rancher

bamboo-docker's Issues

Expose ability to set HTTP/HTTPS in Agent

Currently the only transport protocol supported during install is HTTP.

The user should be able to define what transport protocol to use - e.g. HTTPS or HTTP.

Support for custom agent homedir

The agent should support arbitrary BAMBOO_AGENT_HOME directories passed in as an environmental variable.

Currently the BAMBOO_AGENT_HOME defaults to /root/. With an arbitrary homedir, we can mount this from the Docker host and preform actions on it outside the container

Support for bamboo-capabilities.properties

Bamboo supports setting arbitrary variables in the bamboo-capabilities.properties file of the agent. The format of the file is in the form key=value separated by a return char.

This is useful, for example, to set environment specific variables on the agent. Using these environment specific variables, one can ensure that only certain agents can run certain build and/or deploy jobs. These build and/or deploy jobs can be further restricted down to certain users or groups of Bamboo Server thanks to RBAC.

This means that only certain users can run certain builds/deploys, and these builds/deploys can only happen on certain servers.

It would be nice for this project to support the use of the bamboo-capabilities.properties file

Support for Agent security token verification

Bamboo supports "Security Token Verification" - where the agent passes a, static, token to the server for authentication.

It would be nice for the agent scripts to support these security tokens.

The format for launching with a security token is

java -jar atlassian-bamboo-agent-installer-${AGENT_VERSION}.jar http://${BAMBOO_SERVER}:${BAMBOO_SERVER_PORT}/agentServer/ -t ${BAMBOO_SECURITY_TOKEN}