Reply posted on September 11, 2019 by Linoy AlexanderPega
This is answered in the documentation and in the troubleshooting FAQ.
Collaborate with developers, support engineers, and experts who build and work with Pega products and services. Join us to get fast answers to your questions, and participate in our Ask the Expert sessions!
Congratulations to Kannan Raveendran Nair for achieving the title of Participant of the Week! Kannan believes in sharing knowledge. He proved to be an amazing participant by writing a knowledge share article on a topic that will be informative to the diverse audience in the community. Read his article here. Keep up the great work!
For anyone coming here looking for an answer to this. This feature is now supported as part of Deployment Manager version 4.5- see the announcement for more details.
Hi, Could you please help me to resolve the issue which i have posted in below URL? https://community1.pega.com/community/pega-academy/question/how-create-file-system-repository-devops Regards, Sowmya
You are likely missing the privilege for handling repositories in the PegaRULES:RepositoryUser for the operator that is specified in the DMAppAdmin auth profile, or whichever auth profile you are using for connecting with the environments.
Hi Team, Any offline equivalent to this feature? Or any other way it can be implemented? Any insights will be helpful.
Please follow below link to configuring repositories in Pipeline: https://community.pega.com/knowledgebase/articles/installing-upgrading-and-configuring-deployment-manager-45x#repos Also ensure that repositories configured are accessible across...
If you already have DM 2.1, then you perhaps you already have the existing DM package you can install. However if you have the option, our recommendation would be to upgrade if you can. As noted Version 2.1 has no additional support, but there have ...
Github does not necessarily makes sense as a repository for Deployment Manager. If you are thinking of using Github as a code repository for version control that is not supported. Pega uses the layer cake concept and ruleset versioning as the source...
You can choose to ignore applying the schema change and just approve the manual step. Just make sure that you application won't fail if the schema isn't applied, or that it is being taken care off in some other way. One other thing to double...
We recently updated our FAQs to answer this question: https://community1.pega.com/community/pega-support/question/deployment-manager-faq-troubleshooting-tips Please go thorough the email notifications question and let us know if that solves the issue
Please wait while we search for PDN content that suits your question.