"Power Platform Pipelines" is a newfound feature within the Power environment attracting several tech enthusiasts. As highlighted by Temmy Wahyu Raharjo in his blog post, this feature allows creation and management of developer's environments. For the purposes of his demonstration, Temmy creates three distinct environments.
Set up is rather straightforward - simply navigate to admin.powerplatform.com and select 'Environments,' and then 'Enable Managed Environments.' After that, it's all about the resources and specifically, finding and installing Power Platform Pipelines to your desired host environment (in Temmy's demonstration, the environment is 'temmydev1').
Once installed, users can explore the 'Deployment Pipeline Configuration' app within Power DevOps, where all environments must be initially set up. Details such as environment IDs are obtainable from admin.powerplatform.com. Each environment must be validated and saved before proceeding.
The beauty of these Pipelines is that they can be run with relative ease. By selecting 'Unmanaged Solution' and then clicking the Pipelines icon, you're then provided with deployment information. Following the 'Deploy Here' button, the system can import the solution autonomously while the user waits for the process to complete.
Analysing the solution in the target environment can yield interesting results. Temmy's demo resulted in the solution being imported as a 'Managed' solution, showcasing the efficiency of the process.
In conclusion, Temmy believes this feature is a simplistic ALM tool that doesn't require complex technical skills. However, it does come with minor drawbacks such as rigid compliance with the flow pattern it sets. Despite this, it is indeed a handy feature worth trying out for simpler operations.
Emerging features like the Power Platform Pipelines reflect the persistent evolution in digital technology and tools. These tools simplify complex tasks and provide efficient paths to attain specific goals. In this case, Power Platform Pipelines demonstrates the ease of creating and managing environments even for users with limited technical skills. It's features like these that continue to lower barriers to entry and promote undeterred innovation in the tech community.Read the full article Let’s try Power Platform Pipelines by Temmy
Ever fancied trying out Power Platform Pipelines? Temmy brings you one of the latest features that many have been anxiously awaiting. The need to create three developers' environments to demonstrate and enable the Managed Environments feature is the basic requirement for this mission. Click the provided link to secure your own environment to test and join the Microsoft 365 Developer Program.
Starting up the Managed Environments is a walk in the park. You simply navigate to admin.powerplatform.com, select your environment, then click Enabled Managed Environments. Moving forward, choose your preferred host environment, and proceed to get the deployment pipeline software installed. The function of the host environment is to serve as the primary control and storage for the pipeline.
After the successful installation of the Power DevOps, you'll need to set up all the environments you have. Access the application and proceed to the 'New Environments. Discover the environment variable by going to power-platform admin, select your preferred environment, and get your environment id. It's now time to save everything; if the validation status indicates “Success,” hit next. Otherwise, revisit the previous steps.
Assign roles to the user, permitting the user to become the Pipeline administrator. This is done by giving the user the Deployment Pipeline User and Deployment Pipeline Administrator roles. Now, we are closer to wrapping up your setup. Add the dev environment to the Linked Development Environments, and subsequently proceed to the Deployment Stages.
Create a solution in your Dev environment ready for deployment. Afterward, move on to your Solutions, select the Unmanaged Solution, find the Pipelines icon, and gather the deployment information. You're now ready to try out your pipeline. Time to click the “Deploy here” button, then Next and Deploy. The system will automatically begin the solution import process, which will require some patience to wait for the completion.
Once import is over, assess the solution in the target environment. You can anticipate that the solution will be “Managed.” Now the set up practice is over. The feature is a “low-code” ALM, that is straightforward to set up and does not necessitate possessing technical skills. Nonetheless, you must get used to the as is flow, present in most organizations, meaning you'll need to follow as is flow (a common requirement in the ALM process).
With the ease of setup and simplicity for everyday tasks, it's a feature you'll have to try. Temmy, the KL Power DevOps User Community leader, Microsoft Dynamics 365 Technical Consultant, test-driven developer, and human-code enthusiast expresses joy in CRM-ing as he promises more posts on the subject.
Despite the technical jargon, the process has been gladly simplified to ensure everyone can understand. So, whether or not you're a developer, it's quite simple to understand the workflow. Temmy's expertise in Microsoft's Dynamics 365 Technical Consulting, Temmyraharjo's community leadership, and his impressive coding skills make this blog an excellent resource for understanding Power Pipelines. Stay tuned for more posts on this and related topics.
Temmy pipeline tutorial, Power platform pipelines, learn Power platform, Temmy Power platform guide, Power platform training, get started with Power platform, how to use Power platform, master Power platform with Temmy, Temmy's guide to Power platform, explore Power platform pipelines