Application Configuration #
An application represents a team that manages a group of microservices, non-microservices, mobile apps, or similar workloads to deliver a logically independent functionality. BuildPiper provides a simple workflow to onboard a new application.
1. Application Overview #
| Area | Description |
|---|---|
| Logical Ownership | Applications group services and workloads under a team or functional boundary. |
| Platform Workflow | Platform users can onboard application metadata, policy templates, job templates, VM groups, credentials, regions and clusters. |
2. Add Application #
The Add Application form opens. Fill in the details and click ADD APPLICATION.
Figure 1: Add Application form
| Field | Mandatory | Description |
|---|---|---|
| Application Name | Yes | A unique identifier for the application/team within the platform. |
| Application Description | Yes | A brief description of the application/team. |
| Select Policy Template | Yes | Defines the BP access policy/permission rules. The default template typically creates a few environment specific policies by default. These policies define who can access and modify various BP resources like applications, environment, enable/disable feature, etc. |
| Select Job Template | No | A reusable blueprint that defines the sequence of steps executed to perform a specific task, such as build, deployment, testing, security scanning, infrastructure provisioning, or database operations. |
| Select Version of the job template | No | Allows you to select the appropriate job template version. For example: v.1-stable, v.2-test, etc. |
| Select VM Groups | No | Select the virtual machine group(s) where this application’s VM-based services will be built and deployed. This selection is not required for microservices or mobile applications. |
| Select Registry | No | Select one or more registries at the application level. The selected registries will automatically be available in the VM based Build configuration. |
| Credential | No | The Credential Management component. It provides the necessary SSH keys or IAM roles required to authenticate against the cloud provider. These configurations are used in Non Microservice Application Onboarding. |
| Region | No | The geographic location (for example, us-east-1, eu-central-1) where resources will be physically provisioned. |
| Choose Cluster | No | Choose from the Kubernetes clusters already onboarded in BuildPiper. You can also allocate a dedicated cluster, where all namespaces are mapped automatically, or map only specific namespaces as needed. |
Note: For Select Job Template, select the default job template of non-MS (for example, GLOBAL-NON-MS-TEMPLATE-V3), and select its active version under Select Version of the job template.
3. Application Added #
After you click ADD APPLICATION, BuildPiper creates the application and shows the Application added successfully! message with these checks:
| Check | Status |
|---|---|
| Project Permission Cache Update | Success |
| Default Policy User Group Creation | Success |
Figure 2: Application added successfully
Click VIEW LOGS to see the logs, or click CONTINUE to go ahead.
4. Newly Added Application #
After you click CONTINUE, the newly added application opens on the Service Overview page. The application name is shown in the left navigation. As no service is added yet, the page shows You have 0 services associated with this application. Click +ADD SERVICE to add a service.
Figure 3: Newly added application