=======================================================================
A flexible and configurable docker image to run Atlassian Bamboo. (https://www.atlassian.com/software/bamboo)
Forks Ingensi oracle-jdk Docker image. (https://hub.docker.com/r/ingensi/oracle-jdk/)
======================================================================
-
Edit the Makefile header to specify default values for container variables.
-
In case you need any custom /etc/hosts records to be added, check image/support-files/install.hosts file, and add those records there. Records from this file will be automatically added by container bootstrap on container load.
-
In case you need any CA certificates to be imported into the JVM truststore - specify the download links for them, in image/support-files/install.certificates file. Certificates from this file will be automatically downloaded and imported into JVM truststore on container build.
-
If you wish to build any other version of Atlassian Bamboo - specify the version number in BAMBOO.VERSION file.
-
Run 'make build run'. Container will be built and initialized immediately.
In case this system already has a previous version of this container (say with your current version of Bamboo) data container from it will be automatically remapped to your new container to keep your data intact. Stopping the previous container remains your job though.
Enjoy!
========================================================================
Container takes the following variables.
-
JAVA_OPTS - Arguments to be passed to JVM on startup.
-
CONFIGURE_SQL_DATASROUCE - Whether or not to configure an SQL datasource. If set to 'TRUE', Tomcat, will be configured with an SQL datasource built in. Otherwise, it will not be done and the rest of the fields below regarding the DB connection may be left blank. (default: FALSE)
-
CONFIGURE_FRONTEND - Whether or not to configure Tomcat with proxy awareness. If set to TRUE, Tomcat will be instructed, that it runs behind a reverse proxy. Otherwise, it will not be done and the fields below regarding FE connection may be left blank. (default: FALSE)
-
CONFIGURE_LDAP_AUTH - Whether or not to configure Bamboo with LDAP authentication. If set to TRUE, Bamboo will be instructed to use external LDAP directory for authentication and authorization routines. Otherwise, it will not be done and the fields below regarding LDAP connection may be left blank. (default: FALSE)
-
BAMBOO_DB_DRIVER - Database driver to use.
-
BAMBOO_DB_URL - Database connection URL.
-
BAMBOO_DB_USER - Database user.
-
BAMBOO_DB_PASSWORD - Database password.
-
BAMBOO_FE_NAME - Frontend DNS name, where Bamboo is reachable. (i.e. bamboo.local)
-
BAMBOO_FE_PORT - Frontend port number, where Bamboo is reachable. (i.e. 443)
-
BAMBOO_FE_PROTO - Frontend protocol where Bamboo is reachable. Either 'http' or 'https'.
-
LDAP_HOST - LDAP host to authenticate to.
-
LDAP_PORT - LDAP port to authenticate to.
-
LDAP_BIND_DN - DN to bind to in LDAP.
-
LDAP_BIND_DN_PW - DN password.
-
LDAP_BASE_DN - Base DN for LDAP directory.
-
LDAP_PEOPLE_NS - User namespace (added to LDAP_BASE_DN)
-
LDAP_GROUP_NS - User group (added to LDAP_BASE_DN)
-
LDAP_USERNAME_ATTR - LDAP username attribute.
-
LDAP_USERSEARCH_FILTER - LDAP filter for user search. (incl. membership)
-
MEMORY_LIMIT - Maximum amount of memory that can be used by this container. In megabytes. (i.e. 4096 - means that this container, can use up to 4G of memory)
-
CPU_LIMIT_CPUS - Either a comma separated or a range (X-Y) list of CPU cores where this container is allowed to execute. Enumerations starts with 0. Default 0-2.
-
CPU_LIMIT_LOAD - Maximum load in percents, this container can take from CPU-s under subject. Default 100.
-
IO_LIMIT - A number between 10 and 1000 representing the priority of this containers I/O load in comparsion to all other containers I/O load. Used within container I/O load prioritization. Default 500.