gradle-112

Slide 1: End-to-End Provisioning Architecture Overview
Slide Title: COMET-NAM GUI: Provisioning & Integration Workflow
Subtitle: Streamlined application delivery through interconnected Citi platform dependencies
Core Architecture Concept
Provisioning COMET-NAM GUI via Citi Desktop relies on relational "wiring" between enterprise systems—similar to database referential integrity. Each system validates dependencies downstream before final promotion.
+-------------------+ +--------------------+ +-------------------+ +------------------+
| Jenkins CI | ---> | JFrog Artifactory | ---> | uDeploy | ---> | Deployment Portal|
| Build & Automate | | Artifact Storage | | Version Tracking | | Stream Wiring |
+-------------------+ +--------------------+ +-------------------+ +------------------+
|
v
+-------------------+ +--------------------+ +------------------+
| Citi Desktop | <--- | Background Agent | <---------------------------- | App Directory |
| User Execution | | (runApp.bat Auto) | | Access Control |

Slide 2: Pipeline & Environment Dependencies
Slide Title: System Components & Relational Wiring

1. Build & Release Management (CI/CD Pipeline) • Jenkins CI/CD compiles code and publishes build artifacts. • JFrog Artifactory securely stores versioned binaries. • uDeploy captures release versions, build parameters, and deployment packages.
2. Deployment Portal (Resource & Stream Configuration) • Stream Definition: Connects build artifacts to execution resources. • Resource Binding: Links specific uDeploy application versions, runtime JDKs, and auxiliary dependencies. • Access Mapping: Associates the stream with authorized Atom Groups and their assigned users.
3. App Directory (AppD Portal) (Access Control & Promotion) • One-Time Application Setup: Wires the application, stream configuration, and Atom group affiliations. • Visibility Control: Sets user entitlement and UI display rules. • Environment Promotion: Manages governed workflow approvals for UAT and PROD releases. Slide 3: Release Management Lifecycle Slide Title: Step-by-Step Release & Promotion Workflow [ Step 1: Build Publish ] ---> [ Step 2: Stream Update ] ---> [ Step 3: Approval & Promo ] ---> [ Step 4: Client Sync ] Jenkins / uDeploy Deployment Portal AppD Portal Citi Desktop Operational Steps • Step 1: Build & Publish o Developer pushes changes; Jenkins builds and registers new version numbers in uDeploy. • Step 2: Deployment Portal Update o Deployment Portal Admin updates the target stream with the latest (or selected) version from uDeploy. • Step 3: AppD Portal Governance o AppD Portal Admin submits promotion requests and obtains required approvals for UAT / PROD. • Step 4: User Entitlement & Execution o Authorized Atom group members gain access to launch or update the application. Slide 4: Client Execution & Background Deployment Slide Title: Silent Client Updates & Background Execution Automated Client Lifecycle • Seamless Launch: Users launch COMET-NAM GUI directly from Citi Desktop or Atom. • Zero-Touch Background Installation: o Re-installations and updates execute automatically in the background upon relaunch. o Driven by the custom runApp.bat agent defined within the AppD Portal. • Enterprise Security Benefits: o Eliminates manual installation steps for end users. o Guarantees strict version control and security alignment across all client environments.