Question
Orange Business Services
IN
Last activity: 4 Mar 2025 5:49 EST
looking for GITLAB CI/CD documentation
Hello Team,
I am looking for Gitlab CI/CD documentation for our pega application
Accepted Solution
Updated: 12 Mar 2025 14:30 EDT
Pegasystems Inc.
GB
@purellaS16594611 ⚠ Below is a GenAI-powered answer.
All generated answers require validation against the provided references.
References: GitLab CI/CD Documentation Pega DevOps Architecture Release Management with Pega Platform
1. GitLab CI/CD Setup Documentation
The primary documentation for GitLab CI/CD can be found at GitLab's official documentation. To get started immediately:
- Create a
.gitlab-ci.ymlfile in your repository root - Define your pipeline stages and jobs
- Configure GitLab runners for executing the pipeline
2. Deployment Pipeline Structure
I've created a diagram showing the recommended GitLab CI/CD pipeline structure for Pega deployments:
3. Key Implementation Steps
a) Pipeline Configuration
@purellaS16594611 ⚠ Below is a GenAI-powered answer.
All generated answers require validation against the provided references.
References: GitLab CI/CD Documentation Pega DevOps Architecture Release Management with Pega Platform
1. GitLab CI/CD Setup Documentation
The primary documentation for GitLab CI/CD can be found at GitLab's official documentation. To get started immediately:
- Create a
.gitlab-ci.ymlfile in your repository root - Define your pipeline stages and jobs
- Configure GitLab runners for executing the pipeline
2. Deployment Pipeline Structure
I've created a diagram showing the recommended GitLab CI/CD pipeline structure for Pega deployments:
3. Key Implementation Steps
a) Pipeline Configuration
- Set up environment-specific variables in GitLab
- Configure secure credential management
- Define quality gates and security checks
b) Deployment Automation
- Package application artifacts
- Implement automated testing
- Set up environment-specific deployments
- Configure rollback procedures
c) Security Considerations
- Use GitLab's secret variables for sensitive data
- Implement environment-specific access controls
- Set up audit logging for deployment actions
- Configure security scanning in the pipeline
4. Pega-Specific Configuration
While not using Pega Deployment Manager, you'll still need to:
- Configure artifact repository management
- Set up branch merging automation
- Implement guardrail compliance checks
- Configure test coverage enforcement
5. Required Documentation Links
- GitLab CI/CD Quick Start
- Pipeline Configuration Reference
- GitLab CI/CD Variables
- Security Best Practices
Updated: 20 Feb 2025 5:05 EST
Orange Business Services
IN
Hello Team ,
can anyone help me to get Gitlab CI/CD documentation as soon as possible?
we're planning Orchestrate Pega Deployments using Gitlab CI/CD and Due to some org security reasons we are looking Gitlab CI/CD .Not going with PEGA DEPLOYMENT MANAGER
Accepted Solution
Updated: 12 Mar 2025 14:30 EDT
Pegasystems Inc.
GB
@purellaS16594611 ⚠ Below is a GenAI-powered answer.
All generated answers require validation against the provided references.
References: GitLab CI/CD Documentation Pega DevOps Architecture Release Management with Pega Platform
1. GitLab CI/CD Setup Documentation
The primary documentation for GitLab CI/CD can be found at GitLab's official documentation. To get started immediately:
- Create a
.gitlab-ci.ymlfile in your repository root - Define your pipeline stages and jobs
- Configure GitLab runners for executing the pipeline
2. Deployment Pipeline Structure
I've created a diagram showing the recommended GitLab CI/CD pipeline structure for Pega deployments:
3. Key Implementation Steps
a) Pipeline Configuration
@purellaS16594611 ⚠ Below is a GenAI-powered answer.
All generated answers require validation against the provided references.
References: GitLab CI/CD Documentation Pega DevOps Architecture Release Management with Pega Platform
1. GitLab CI/CD Setup Documentation
The primary documentation for GitLab CI/CD can be found at GitLab's official documentation. To get started immediately:
- Create a
.gitlab-ci.ymlfile in your repository root - Define your pipeline stages and jobs
- Configure GitLab runners for executing the pipeline
2. Deployment Pipeline Structure
I've created a diagram showing the recommended GitLab CI/CD pipeline structure for Pega deployments:
3. Key Implementation Steps
a) Pipeline Configuration
- Set up environment-specific variables in GitLab
- Configure secure credential management
- Define quality gates and security checks
b) Deployment Automation
- Package application artifacts
- Implement automated testing
- Set up environment-specific deployments
- Configure rollback procedures
c) Security Considerations
- Use GitLab's secret variables for sensitive data
- Implement environment-specific access controls
- Set up audit logging for deployment actions
- Configure security scanning in the pipeline
4. Pega-Specific Configuration
While not using Pega Deployment Manager, you'll still need to:
- Configure artifact repository management
- Set up branch merging automation
- Implement guardrail compliance checks
- Configure test coverage enforcement
5. Required Documentation Links
- GitLab CI/CD Quick Start
- Pipeline Configuration Reference
- GitLab CI/CD Variables
- Security Best Practices
Orange Business Services
IN
@MarijeSchillern Hello
Do we need any specific file locations for pega to implement Gitlab ci cd deployment?
Pegasystems Inc.
GB
@purellaS16594611 from our GenAI bot:
Below the essential file locations and structure requirements:
@purellaS16594611 from our GenAI bot:
Below the essential file locations and structure requirements:
Required File Locations
- Root Configuration File
- The
.gitlab-ci.ymlfile must be placed in the root directory of your repository - This is the primary configuration file that GitLab uses to manage your CI/CD pipeline
- The
- Pega Application Files
- Place your Pega application files in a dedicated
/pegadirectory within your repository - Organize deployment configurations in a
/deploysubdirectory - Store environment-specific variables in
/deploy/environments
- Place your Pega application files in a dedicated
- Pipeline Configuration Files
repository-root/├── .gitlab-ci.yml├── pega/│ ├── application/│ └── rules/├── deploy/│ ├── environments/│ │ ├── dev/│ │ ├── staging/│ │ └── prod/│ └── scripts/└── tests/
Important Considerations
- Artifact Storage
- Configure artifact storage in your GitLab settings
- Use the built-in GitLab artifact registry or an external artifact repository
- Ensure the pipeline has appropriate access permissions to artifact storage locations
- Security Files
- Store security credentials as GitLab CI/CD variables, not in repository files
- Place security scanning configurations in
.gitlab/security/directory - Keep authentication tokens and sensitive data in GitLab's protected variables
- Temporary Files
- GitLab runners use temporary storage during pipeline execution
- Don't rely on persistent storage in pipeline jobs
- Use GitLab artifacts for passing files between pipeline stages
Remember that when transitioning from Pega Deployment Manager, you'll need to ensure your file structure accommodates both your existing Pega deployment requirements and GitLab CI/CD best practices.
References:
Orange Business Services
IN
@MarijeSchillernAnyway we should require Pega Deployment Manager to automate CI/CD on premises environment rigth?
Does Pega Deployment Manager comes under pega license or do we need to pay extra for this?
Updated: 4 Mar 2025 5:49 EST
Pegasystems Inc.
GB
@purellaS16594611 From our GenAI bot:
Regarding your first question about whether Pega Deployment Manager is required to automate CI/CD in on-premises environments: While Pega Deployment Manager is not explicitly required, it is the standard tool provided by Pega for automating DevOps workflows, including CI/CD for Pega applications. It provides a low-code, model-driven experience to configure and run continuous integration and delivery workflows. Deployment Manager is designed to expose all the capabilities of Pega Platform necessary for automating DevOps workflows, including branch merging, application packaging, applying quality gates, and promoting applications to different environments.
As for your second question about licensing: you should speak to your Pega Account Executive about this.
I believe that Pega Deployment Manager is included in the standard Pega license for on-premises environments, but you will need to check.
For on-premises deployments, you have several options:
- Running the open-source version
- Using a solution from a third party
- Getting the service through a partner that will run a third-party solution
If your organization already has an enterprise license for a third-party product that can serve this purpose, you can set up an instance dedicated to supporting your Pega applications, provided that the terms of your agreement permit it.
References:
@purellaS16594611 From our GenAI bot:
Regarding your first question about whether Pega Deployment Manager is required to automate CI/CD in on-premises environments: While Pega Deployment Manager is not explicitly required, it is the standard tool provided by Pega for automating DevOps workflows, including CI/CD for Pega applications. It provides a low-code, model-driven experience to configure and run continuous integration and delivery workflows. Deployment Manager is designed to expose all the capabilities of Pega Platform necessary for automating DevOps workflows, including branch merging, application packaging, applying quality gates, and promoting applications to different environments.
As for your second question about licensing: you should speak to your Pega Account Executive about this.
I believe that Pega Deployment Manager is included in the standard Pega license for on-premises environments, but you will need to check.
For on-premises deployments, you have several options:
- Running the open-source version
- Using a solution from a third party
- Getting the service through a partner that will run a third-party solution
If your organization already has an enterprise license for a third-party product that can serve this purpose, you can set up an instance dedicated to supporting your Pega applications, provided that the terms of your agreement permit it.
References: