Objective
You have a Java application that is built with Maven and the source code is managed in a GIT repository. The goal of this tutorial is to automate the build and deployment across multiple environments. This automation will include:
...
Select Topology from the menu and then select Topology Overview from the left menu. You will see a table that has Instances as the rows and Environments as the columns with colored circles representing the Environment Instance. Color coding represents:
...
Selecting the GREEN circle for DEV will display the configurable properties/Endpoint and allows for the configuration of the properties.
...
The Build Request Form will appear and we need to:
select the environment we want to build the application in, the environments that had the Build Environment checkbox will appear in the dropdown.
select the SCM Branch that was configured on the project, this will be pre-populated if there is only one configured Branch.
submit the request, this will initiate the mavenBuild workflow.
...
Upon submission, the build workflow is initiated and the workflow steps are executed on the Maven instance in the BLD environment, utilizing the LOCALHOST endpoint. Upon completion of the workflow, the execution status will be successful. More information about the workflow execution can be viewed from the Execution Id link.
...
The Deploy Request Form will appear and we need to:
Select the Project Version. The form will default to the latest Project Version but the dropdown will contain all previously create Project Versions.
Select the Environment that the deployment will be executed in.
Select the Deploy Instance, which will be defaulted from the Project configuration. Deployments can happen on multiple instances.
Submit the request, which will initiate the application Deploy workflow.
...
Upon submission, the deploy workflow is initiated and the workflow steps are executed on the TOMCAT InstanceTarget Group in the DEV environment, utilizing the TEPLT01endpoint. Upon completion of the workflow, the execution status will be successful.
...
The Execution Id is a link to all of the execution data related to each request, such as
the workflow execution steps
the logs for each workflow step, which can be viewed by clicking on the link under the step
the artifact, which can be downloaded
the project and environment instance property values at the time of execution
...
Congratulations! You have successfully completed the Java Tomcat Application tutorial.
...