Question
FBI
US
Last activity: 22 May 2024 11:48 EDT
Migrating Jenkins pega import pipeline to gitlab runner
Hello our team is currently working on using a gitlab pipeline to do our imports. we have one created for Jenkins but want to consolidate and use gitlab runner. I know that prcp utils is a package that required but wanted to see if there where any examples of using gitlab runner and what are some pit falls and pointers on using gitlab runners for pega and other use cases
Accepted Solution
Updated: 22 May 2024 11:48 EDT
Pegasystems Inc.
GB
o use GitLab runner for Pega imports, you can leverage the prpcServiceUtils tool, similar to how you would in a Jenkins pipeline. You can create a GitLab CI/CD pipeline and use GitLab runner to execute the jobs. In terms of pitfalls and pointers, here are a few to consider:
- Ensure that the GitLab runner has access to the prpcServiceUtils tool and all its dependencies.
- Make sure to handle error conditions in your pipeline scripts. The prpcServiceUtils tool returns specific exit codes for different types of errors, which can be used to control the flow of your pipeline.
- If your Pega Platform and GitLab runner are not on the same network, ensure that the necessary firewall rules and routing are in place for the runner to be able to reach the Pega Platform.
- Keep your pipeline scripts as simple as possible and make use of GitLab's built-in features for handling common tasks, such as artifact management and caching.
Please note that while the prpcServiceUtils tool is designed to be used with any CI/CD tool that can run command-line scripts, there may be specific nuances or features of GitLab runner that are not directly supported by the tool.
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
o use GitLab runner for Pega imports, you can leverage the prpcServiceUtils tool, similar to how you would in a Jenkins pipeline. You can create a GitLab CI/CD pipeline and use GitLab runner to execute the jobs. In terms of pitfalls and pointers, here are a few to consider:
- Ensure that the GitLab runner has access to the prpcServiceUtils tool and all its dependencies.
- Make sure to handle error conditions in your pipeline scripts. The prpcServiceUtils tool returns specific exit codes for different types of errors, which can be used to control the flow of your pipeline.
- If your Pega Platform and GitLab runner are not on the same network, ensure that the necessary firewall rules and routing are in place for the runner to be able to reach the Pega Platform.
- Keep your pipeline scripts as simple as possible and make use of GitLab's built-in features for handling common tasks, such as artifact management and caching.
Please note that while the prpcServiceUtils tool is designed to be used with any CI/CD tool that can run command-line scripts, there may be specific nuances or features of GitLab runner that are not directly supported by the tool.
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
Using prpcServiceUtils and Jenkins for automated application deployment
Ask the Expert - Pega Deployment Manager with Meenakshi Nayak (PegaWorld '23
Automating Pega deployments using Jenkins and prpcserviceutils tool