About the delivery
ProsessPilotene delivered Power Platform Pipelines - Personal Pipeline - For solutions/solution files for Noova Energi System AS (2024).
“Pipelines for all”, a personal pipeline (which can be shared). Never tested before. It is being used here to gain experience and to compare it with the pipeline otherwise used for solution deployment.
Runs upgrades for complete solutions, works well.
New environment variable: Specifies a new value in the target environment during import. - not tested with values, only with the “default value”, which is recommended to be removed before import.
Running the patch: works fine—it is applied as expected. It also handles rerunning the same patch without issues. Increases the version number as expected.
Value creation
None. Only testing functionality that has already been implemented in the form of yaml-pipelines.
Very quick and easy to get started. Gets a deployment pipeline up and running in a couple of minutes.
Lower startup costs. This can help lower the threshold for launching projects. It can then be expanded as needed.
The solutions
- Power Platform Pipelines - Personal Pipeline - For solutions/solution files
Power Platform Pipelines - Personal Pipeline - For solutions/solution files: Can be used in Managed Environments
Set up in just a few clicks, with support for solution export and import, rollback, and mapping of environment variables and flows.
Pre-validation of content to avoid wasting time on dependencies.
Mentioned as potential extensions: Importing multiple solutions simultaneously (one release, multiple solutions)
Possible support for combining with data
The pipeline uses “Overwrite customizations” set to true
Area and keywords
Other
Deploy,Solution,Import,Export,Solution,ALM, ×
Limitations
No option to link directly to work items or interact with Azure DevOps. Any work items can only be referenced in text form.
It is not possible to update an existing patch. Tested with the same and an incremented version number. It is possible to apply a new patch.
Seems to only use “Best practices”. Limited configuration options, “use/do not use”, cannot specify that it should run update rather than upgrade, etc. (perhaps not an issue?)
Version control cannot be stored in git, only together with the environment → Risk (?) - This has not been a problem, so it is probably something we can live with.
“Personal pipeline” is the only option currently available. It only supports 3 steps; four are not possible.
A single step cannot be used for both import and export → a layered solution approach is not possible