Now that Pega platform releases are coming with increasing frequency, would you consider providing a Maven repository containing the individual PRPC EAR-file components as versioned downloads so that environments can be automatically built and upgraded by DevOps CI/CD tools, such as Maven?
This would reduce the number of manual installation steps and make it easier for DevOps teams to include, for example, MDB modules in the EAR-file for deployment.
We are currently unpacking Pega EAR-files and putting the resulting WAR, RAR and EJB modules as well as dependent JAR-files into Artifactory using the "Implementation-Version" build id available in the Manifest.mf, but as patches are released more often the need to automate this is increasing as well.
No takers? Too bad.. I think providing a Maven repository could really have lifted the Pega PRPC installation and configuration process to the next level for on-prem installations. But as I see no replies to this thread and Maven metadata now being stripped from 8.2 binaries, I guess I should never have asked.
Posted: 4 years ago
Posted: 18 Apr 2019 12:16 EDT
Dave Casavant (casad)
Senior Director, Cloud Architecture
Rather than providing the bits and pieces to construct a deployment image, we are now providing a standard Pega Platform Docker image as of 8.2. More information can be found here: https://community.pega.com/knowledgebase/articles/cloud-choice. This has a number of advantages over individual artifact availability and based on customer feedback we have found that the complete turnkey solution is the easiest to run with. If you have feedback, please feel free to reach out!