Use Cases
Custom CI/CD Pipeline
Use your own CI/CD pipeline to build the Docker images. In order to do this, use the following Jenkins flow and execute the scripts with required parameters.
- Use the build.sh file. In the tml-installer, this file is located under /var/jenkins_home/docker-build.
- build.sh internally calls the individual component's Docker image builder script build - <tml_component_type>.sh under tmgc-<tml_component_type>. In the tml-installer, this file is located under /var/jenkins_home/docker-build/tmgc_<component_type>. For example, to build a NoSQL Docker image, the build.sh script internally calls build-nosql.sh.
- To create the Docker image, each component's builder script uses Dockerfile.<tml_component_type> and create_<tml_component_type>.sh. For example, to build a NoSQL component Docker image, use Dockerfile.nosql and create_nosql.sh.
Use Third-Party Software
You can install third-party software by updating the <tml_component_type>-install.sh script located under docker-build/install.If the package is not available through yum, create a repo file under
var/jenkins_home/docker-build/tmgc/install/ with required package under
tmgc-rpm. Update the
<tml_component_type>-install.sh script as follows and install it.
cp /home/builder/docker-build/<your_repo_file> /etc/yum.repos.d
If the package is available through yum, add the command to the installation script. For example:
<tml_component_type>-install.shTo install vim-enhanced on the Cluster Manager component, add the command yum install vim-enhanced.x86_64 in cm-install.sh.
Copyright © Cloud Software Group, Inc. All rights reserved.