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

 Ross McIvor (RossM448) CWT
CWT
GB
RossM448 Member since 2020 1 post
CWT
Posted: May 20, 2020
Last activity: May 25, 2020
Posted: 20 May 2020 10:52 EDT
Last activity: 25 May 2020 3:35 EDT
Closed

Source Control Inside PEGA Customer Service

Hey guys,

We are currently building a product on PEGA CS, and there are some problems with Source Control. Can you please go over the functionality in terms of source control and management.

We are trying to understand why there is no merge option available and work constantly gets overwritten by another team.

 

Thanks in advance

To see attachments, please log in.
Pega Customer Service 8.2 DevOps Other Industry

Posted: 4 years ago
Posted: 25 May 2020 3:35 EDT
Anil Kondakindi (konda) PEGA Director, Internal Development Experience
Pegasystems Inc.
IN

Hi,

Are you using branch based development? If yes you would have the option to merge and changes would not be merged if there are conflicts with each others changes. Here are some best practices: https://community.pega.com/knowledgebase/articles/devops/84/understanding-development

We have deployment manager  as exchange component, which helps you manage your application release cycle and promoting it to production. Refer to its documentation for additional details. If you are on pega cloud you can request for a deployment manager instance.

 

Regards,

Anil

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