Configuring an application
There are a few requirements and recommendations for structuring an application that
is being managed using Deployment Manager. See this brief overview to get
started with configuration. The PegaDevOpsFoundation application provides the capabilities to execute pipeline
tasks and adds pipeline integration to the Dev Studio and App Studio. Any application that is being managed by Deployment Manager must include it as a built-on application. New applications only need to be updated on the development environment. Deployment Manager is capable of migrating
the whole application to new environments as part of deployment pipelines. If the application has already been deployed to all environments, it is required to
manually update the application record on each environment to be built on
PegaDevOpsFoundation. The next deployment will sync up the
application changes and will result in an aged update message on Deployment Manager. The target application is regularly packaged and promoted to higher environments so
it is important to exclude branches and any other work in progress. A development
layer consists of: Development layers can be assigned to developers as needed, whether it is one per
application, team or developer. Using a development layer also allows you to keep the target application locked to
prevent unintentional changes. Testing assets are managed by Deployment Manager pipelines, but
they are only deployed to a subset of environments. To manage and run test cases it
is necessary to create a test layer. A test layer consists of: If you have followed all the recommendations in this article, you should end up with
an application that is structured like the one seen below. If you are using branches in either a distributed or non-distributed branch-based
environment, configure the development system so that you can start deployments when
branches are merged. Configuring the development system includes defining the URL of the
orchestration server, creating development and target applications, and locking application
rulesets. For more information about dynamic system settings, see Creating a dynamic system settingAdd PegaDevOpsFoundation as a built-on application
For new applications
For applications that have already been deployed to all environments
Create a development layer
Create a test layer
Summary
Configuring the development system for branch-based development in 5.1.x
Previous topic Securely authenticating in Deployment Manager Next topic Migrating data to Deployment Manager 5.x