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

 Larry T (LarryT)
Frontier Communications

Frontier Communications
US
LarryT Member since 2017 20 posts
Frontier Communications
Posted: Jan 8, 2018
Last activity: Feb 7, 2018
Posted: 8 Jan 2018 13:35 EST
Last activity: 7 Feb 2018 11:07 EST
Closed

Parallel Development

In parallel development process we need to create a Application Team built on a main application.. Why don't we just add branch direct to main application?

why do we need a Application Team in play for parallel development?

Thanks

Larry

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

  • Guangri Liang
Posted: 6 years ago
Posted: 9 Jan 2018 12:49 EST
Rodrigo Amorim de Sant'Ana (rodrigoamorim)
Capgemini
Solution Architect
Capgemini
BR

Hi LarryThai, it could be done just adding branches.

But if the main point is to isolate the development streams, it wont work well.

Different teams will be able to see each other's work.

And multiple branches in the same app may create dependency between them.

With an independent app for each team we asure that :

  • the development will be built over a "immutable" version and,
  • each branch can be delivered as soon as the works finishes

 

To see attachments, please log in.
Posted: 6 years ago
Posted: 31 Jan 2018 18:33 EST
Aruun Kumar (ARUUNKUMAR)
American Express
Sr. Engineer
American Express
US

Hi RodrigoA6031, Can you clarify the 2 reasons you've mentioned with an example?

1. What is the need for an 'immutable' version? If Team A & Team B are working in their own corresponding branches and if Team B is complete and ready to release, cant they just merge their changes to the base application and release without impacting Team A? 

2. How does having separate Team applications help faster delivery?

However one other advantage I can think of by having a team application is from an access standpoint as this will enable creation of specific AccessGroups and hence provide the needed isolation.

 

To see attachments, please log in.
Posted: 6 years ago
Posted: 1 Feb 2018 7:11 EST
Rodrigo Amorim de Sant'Ana (rodrigoamorim)
Capgemini
Solution Architect
Capgemini
BR

Hi ARUUNKUMAR,

1. A simple example: imagine that we have two teams working over the same base version. One is changing a flow, and the other need to fix a bug in the same flow. If they are working in the same application. The bug fixing may be compromissed by the flow changes. The called immutable version would be something like a base version for multiple development streams.

2. Not a faster delivery, probably more assertive. Agility is more about saving time than speed.

 

To see attachments, please log in.
  • Santo Quattrone Tom Zhang Domenico Fodaro
Posted: 6 years ago
Posted: 12 Jan 2018 8:36 EST
Lee Pederson (pedel) Engagement Strategy Content Expert & Principal Instructor - LSA
Pegasystems Inc.
US

Plus the number of branches defined against a single application should not become excessive for performance reasons.  The PDN article below describes a layered approach that leverages multiple built-on applications.

https://docs-previous.pega.com/devops/84/understanding-best-practices-devops-based-development-workflows

To see attachments, please log in.
Posted: 6 years ago
Posted: 7 Feb 2018 11:07 EST
Rajeesh Shenoy (RajeeshRS)
American Express
Senior Engineer
American Express
US

Create Branch for parallel development. We can also create a new application based on the situations and built on based app.

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