Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Sivaram Chatla (SivaramChatla)
Infosys

Infosys
NL
SivaramChatla Member since 2013 1 post
Infosys
Posted: Mar 28, 2019
Last activity: Jul 17, 2019
Posted: 28 Mar 2019 8:27 EDT
Last activity: 17 Jul 2019 11:37 EDT
Closed

Publishing Branch to repository

Dear All,

I have created sample application AAA in which i have created branches and added few rules.

I have published branches to respository , but when i login to Deployment manager portal i am not able to view branches which i published.

Configruation done.

1. Using Amazon S3 repository as artifact in both pipeline setting and while publishing branch.

2. Sample application AAA is built on PegaDeploymentManager application

3. Added AAA application in pipeline setting.

Please help me on this how to see published branches in Deployment manager.

Thanks in advance.

***Edited by Moderator Marissa to move from Pega Academy to Pega Support Community; update platform capability tags***

To see attachments, please log in.
Low-Code App Development
DevOps

Posted: 5 years ago
Posted: 17 Jul 2019 11:37 EDT
David Picariello (picada)
PEGA
Senior Manager, Services Engineering, Application Logic
Pegasystems Inc.
US

I'll answer this question, in general. Hopefully, it will be applicable in your case.

In Deployment Manager, when you start a build it stores your artifacts in a directory specific for that pipeline and environment (Dev/Prod). When you publish from Pega, it stores it in the path described in the Repository rule. I'm assuming that these are two different paths and I would not recommend publishing directly to the path for your pipeline because that will likely just cause confusion.

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice