Set up Pipelines in Power Platform
What is Pipelines for Power Platform?
Benefits:
Pipelines bring significant benefits to teams or organizations looking to adopt healthy, automated ALM (Application Lifecycle Management) processes. With pipelines, the effort and expertise required to achieve a good return on investment (ROI) for ALM is significantly reduced.
Admins can now quickly and easily set up automated deployment pipelines in just a few minutes, as opposed to the days or weeks previously required. This makes it easier to manage deployments and updates, reducing the time and effort required.
For makers, pipelines provide an intuitive user experience that simplifies the process of deploying their solutions. This allows for faster testing and iteration, making it easier to bring new features and updates to market.
Professional developers also benefit from pipelines, as they can optionally run pipelines using their preferred tools, such as the Power Platform command line interface (CLI). This provides a more customizable and flexible approach to managing ALM, enabling developers to tailor their workflows to their specific needs.
Create a Pipeline:
Choose Environments for Pipelines:
Development
environment.
This is where you’ll develop solutions. A pipeline can be run from within any
development environments linked to it.
·
Target environment. The destination environment(s) a
pipeline deploys to. For example, integration testing, UAT, production, etc.
Steps:
c) Select the Host Environment (Which will contain all the configuration for the pipelines).
1.
Once the Deployment Pipeline package
installation has completed, go to Power Apps, then select the dedicated host
environment (where you installed the application).
2.
Play the Deployment Pipeline Configuration app.
3.
Select Environments on the left
pane, and then select New to create the environment records in
Dataverse:
·
Name: Enter the name for the environment record. It's a good idea to include
the same name as the actual environment, such as Contoso Dev.
·
Environment Type: Select either Development Environment or Target
Environment. Select Development Environment for all source
environments where unmanaged solutions will be developed. Select Target
Environment for QA and production environments where the managed solution
artifacts will be deployed.
·
Environment Id: Paste in the environment ID that you copied in the earlier step.
4.
Select Save.
5.
Refresh the form, then verify Validation
Status equals Success.
6.
Repeat steps 4-6 until all environments that will
participate in the pipeline have environment records created.
7.
Select Pipelines on the left
navigation pane, and then select New to create a new
deployment pipeline:
·
Name: Enter a name for the pipeline, such as Contoso Standard
Deployment Pipeline or Contoso Hotfix Pipeline.
·
Description: Optionally, enter a meaningful description for the pipeline.
8.
Within the Linked Development Environments grid,
select Add Existing Development Environment, then associate one or
more development environments. Note that a pipeline must have at least one
development environment and one stage before it can be run.
9.
Within the Deployment Stages grid,
select New Deployment Stage, to display the quick create
pane.
10. Enter the details for each stage, and then select Save and Close:
·
Name: The name of the stage.
·
Description (optional): Optional description for the stage.
·
Previous Deployment Stage (optional): Specifies a deployment stage that must be deployed to
before deploying to the current stage. For example, when creating a production
stage, you can add the test stage as the Previous Deployment Stage.
Note that for the first stage, or pipelines containing only one stage, this
should be left blank.
·
Target Deployment Environment: This is the target environment where this stage will deploy to.
11. Repeat the previous two steps for each stage you'd like to add to the
pipeline. Note that you must have at least one stage. You can add up to seven
stages.
Grant access to edit or run pipelines
Pipeline security is managed within the host
environment by assigning security roles. Additionally, users must currently
have access to all environments associated with a pipeline in order to create
or run the pipeline.
When you installed the Power Platform pipelines
application, two security roles were added:
·
Deployment Pipeline User: Has privileges to run pipelines that have been shared with them.
·
Deployment Pipeline Administrator: Has full control over all pipeline configuration, without needing system
administrator security role membership.
Share pipelines with makers
The Deployment Pipeline User security
role grants access to run one or more pipelines. It doesn't grant access to
create, edit, or delete pipelines. Users with the Deployment Pipeline User
security role won't see the host environment within the environment picker in
Power Apps or Power Automate, or otherwise need to be aware of it.
To share pipelines:
·
Assign makers the Deployment Pipeline User security
role within the host environment. This security role is installed with the
Power Platform pipelines application. More information: Assign a security role to a user
·
In the deployment pipeline configuration app, Share the
pipeline record with makers (or Azure Active Directory groups). Read privilege
is sufficient to view and run a pipeline from within the development
environment. More information: Share rows with a user or team
·
Makers must also have privileges to export solutions
from the source development environments, as well as privileges to import
solutions to the target test and production environments for which the pipeline
deploys to. By default, system customizer and environment maker roles have
these privileges.
Comments
Post a Comment