Deployment Manager success stories from our users
Deployment Manager community,
We engage directly with you, our users, regularly and you will often tell us stories of success, or surprise us with a configuration or use case we had not yet encountered.
Also, when interacting with customers inquiring about Deployment Manager we're asked for references of what other users have accomplished or whether their unique requirements have been adopted successfully.
I'm hoping to give members of the community a platform to share their experiences here so we can all learn from eachother directly.
Please post your experiences, especially if:
- You have integrated Deployment Manager with other third party tools.
- You have a unique environment or process configuration that others may be interested in.
- Deployment Manager has helped you automate formally manual process that has caused significant improvement in lead time of deployables.
If instead you want to bring attention to something that you have struggled with; I have created a seperate discussion for that.
-Ryan
Updated: 21 Feb 2020 14:29 EST
Pegasystems Inc.
US
I will start this off by telling you bit about how we use Deployment Manager to build Deployment Manager itself because we do have a couple unique requirements of our own. The build which can be downloaded on the exchange is generated as the result of a Deployment Manager deployment.
Here are some high level details about our process:
- We've had up to three teams who contribute to Deployment Manager in varying degrees.
- Teams merge throughout their sprint; each bug gets it's own branch, each story (intended to be a small increment of work) gets it's own branch and is merged as soon as it is completed.
- We use remote development environments which teams spin up and manage on their own. We generally have one in the US, and one in India.
- We have two active pipelines for each release; one for PegaDeploymentManager and a second for the PegaDevOpsFoundation.
- Our pipeline is configured to run PegaUnits as part of the CI (pre-merge) process and then run a suite of JUnits post merge using a Jenkins job.
- Both pipelines are configured to run a Jenkins job that takes both the applications, API documentation, and installation documentation and generates an archive.