How to connect two environments of one Power Automate platform with Azure Devops to perform import task from azure devops to import solution zip file from one environment of Power Automate to another environment
Related
My VMs all have Azure DevOps agents installed on them to automate deployments. We have a need to automate runbook tasks on these agents as well, and are investigating Azure Automation as a solution.
However, I would prefer not to have to install two agents on every VM. Is there a way to have Azure Devops and Azure Automate share an agent on a single VM?
I suppose that you could test to create a combination with Azure DevOps and Azure Automation.
And the key to for the integration is creating a service connection from Azure DevOps to Azure Resource Manager.
And you could try to finish your Azure Automation Deployment with Azure Powershell task in a release pipeline.
And you could refer to this blog for more detailed instructions. USING AZURE DEVOPS PIPELINES WITH AZURE AUTOMATION
welcome community.
currently, our customer has Dynamics 365 On-premise infrastructure, additionally more connected applications to CRM. All is available thru VPN.
Case is to implement CI/CD process. i would like to use AzureDevOps Cloud.
Code management solutions = bitbucket.
Of course its not a problem to implement full ci/cd process within OnPremise Dynamics but the question is HOW we manage to bypass VPN?
i have found some tips in MS documentation with Agents and more but i am not sure if this will work.
any suggestion? thank you
If you are using Dynamics 365 On-premise. You will need to configure self-hosted agents on your local machine. See here for detailed steps.
Since D365 is behind a proxy. You will need to configure your self-hosted agent to run behind a web proxy. See detailed steps here.
There is no need to install Azure devops server. You just need to configure your azure pipeline to run on your self-hosted agent created in above steps. So that your azure pipeline can access to the on-premise resources.
When you configure your pipeline(see below for more information about configure pipeline), Choose the Agent pool(Default for below example) where the self-hosted agent resides to run your pipeline on your self-hosted agent.
You need to create azure pipeline for CI/CD process within azure devops.
Below are the examples in detailed steps to configure a classic pipeline in azure devops to implement CI/CD for Dynamics 365.
1, CI/CD for Dynamics 365 CE using Azure DevOps
2, Build Azure DevOps Pipelines for Dynamics 365 CRM/Power Platform
If you are to configure release pipeline for CD process. You probably will need to create deployment groups to deploy to on-premise D365. See here to provision agents to deployment groups.
3, Check D365 forum for more threads about integration D365 with azure devops.
You will much likely encounter some problems while configuring azure pipeline. Please raise new threads about each specific problem your encountered in configuring azure pipeline.
I have a nodejs web application that I build in Azure Pipelines. I am planning to deploy the generated artifacts on a Azure VM (probably a dev test labs), as part of one of the pipeline steps.
I want to now run browser tests by pointing the browser to the hosted URL in the Azure VM. I want to use the Azure windows and linux VMs in a build pipeline to run the tests on this remote Azure VM and publish the results to the pipeline. These would be karma tests essentially running on the nodejs server.
In my current design, the test results are going to be available on the Azure VM hosting the nodejs application.
What I don't understand is how can I get these test results back to
the Azure Pipeline for publishing the same?
Is there a way I can architect this solution without having to setup my Azure VM as a
pipeline agent in Azure DevOps?
Is there a standard pattern to design such continuous test infrastructure using Azure DevOps?
Thanks
According to your description, you just want to use Microsoft host agent to access an url on your self-host agent (ignore it's Azure VM or your own physical machine, same to host agent).
It depends if that url are accessible through public internet.
The simplest solution here is deploy your build agent on that Azure VM directly. Then run build and test. You can do this through the following script and tasks:
run ng test or any command to raise your tests
publish test results with PublishTestResults task
publish code coverage results with PublishCodeCoverageResults task
Microsoft-hosted agent pool will not work for you with every scenarios. For many teams this is the simplest way to run your jobs. You can try it first and see if it works for your build or deployment. If not, you can use a self-hosted agent. Self-hosted agents give you more control for your builds, tests and deployments.
In your scenario, setup your Azure VM as a pipeline agent and run build/test on it should be the simplest and convenient solution.
I am trying to figure out how to import my external test results into Azure DevOps.
This article describes how to publish the results within the same pipeline. But that's not going to help me. We do use Azure pipelines to build and deploy our solution, but the testing is run after that (in a deployed environment), so, outside of the pipeline. We can collect the results (in a Azure DevOps suitable format) and would like to feed it back into Azure DevOps release that did the deployment.
All tips are welcome.
I am working for a WPF application, and recently I have migrated TFS to Azure DevOps and I am successfully able to create build artifacts as well, unfortunately, I could not create executable from the artifacts as Azure DevOps does not support InstallShield Package creation with it, now I decided to move the build artifacts to my local build server,again my company law doesn't allow to access my server from outside network, what should do to create executable.
The Build Agent needs to be able to connect to Azure DevOps. It's enough for it to be able to make an outgoing connection over https (443). The agent can be configured to connect through a web proxy server.
What alternatives do you have:
Use the hosted agent and install InstallShield as part of the build process. This will be slow, but it is doable. You'll need to execute this step as part of every build that tries to create the InstallShield package and requires you to do a head-less installation of InstallShield (given that they are the kings of Installers, I suppose this is doable).
Use a private agent in Azure. You can spin up any IaaS server on Azure, install Visual Studio, InstallShield and the Azure DevOps Agent on it and use it as a build server. There is a set of standard images file available which you can use as a basis.