Question
Ascensus
Ascensus
US
Ascensus
Posted: Aug 6, 2025
Last activity: Aug 17, 2025
Last activity: 17 Aug 2025 22:54 EDT
Pega Integration with ADO(Azure Dev Ops) for end to end CI/CD
Is anyone successful in integrating Pega with ADO (Azure Dev Ops). I learnt that ADO has Open API Library that we can use to connect to ADO from Pega but i am trying to understand is on how we can use ADO for end to end CI/CD integration Like having an User story in ADO and once Dev complete, Have the ADO to execute a pipeline for merging the code in Dev and preparing a RAP file to deploy it to QA region, post QA completion the ADO US# must be updated with status 'Ready to PROD" and then deploy the product to PROD, perform smoke testing in PROD and update the respective US# with Prod deployed status .
would be interested to hear and know from the community who has been successful here.
Posted: 6 months ago
HCA Healthcare
HCA Healthcare
US
@anwar.shaik
Yes this works well with Azure DevOps using Pega Deployment Manager (PDM) or prpcServiceUtils/Pega CLI from ADO pipelines. Set ADO as the orchestrator: trigger on user story move or PR merge, then call PDM pipeline stages (Dev → QA → Prod) via REST, or run Pega CLI to export/import a Product (RAP). In Dev, build the ruleset using branch merge, generate the RAP, and publish it as a pipeline artifact. In QA, run PegaUnit, guardrail, and scenario tests; fail fast on errors and post results back to the ADO build summary. Use ADO service connections/variables to store Pega credentials and target URLs; parameterize app, ruleset, and version. After each stage, call ADO Work Items API to set the user story state (e.g., Ready for Prod, Deployed to Prod) and add deployment notes. For Prod, add manual or approval gates, import the RAP, run smoke tests (Scenario tests or lightweight API checks), and capture logs as artifacts. Use webhooks from PDM to notify ADO, or have ADO poll PDM job status for synchronous control. Keep environments consistent (pipeline JSON in PDM, Product rules, access), and version everything so rollbacks are a single RAP redeploy.