I have two projects in azure, need to trigger pipeline from pipeline in the another project. I installed the extension 'triggers azure devops pipeline' from marketplace.
Please help me with configuring this extension in the yaml file
[Please see the screenshot of my yaml file and extension]: https://i.stack.imgur.com/RGOJ4.png
The azure devops service connection dropdown of the 'triggers azure devops pipeline' extension is not displaying any value
According to your screenshot , it seems that you haven't created a Azure Devops API service connection.
You could navigate to Project Settings -> Service connections and create a Azure Devops API service connection.
Note: the Personal Access Token needs the following rights:
1.Triggering a Release: Release – Read, write & execute – Build Read & Execute
2.Triggering a Build: Build Read & Execute
Then you could get the Azure Devops Service Connection in the target task.
For more information, you could refer to the introduction of the extension.
Hope this helps.
Related
I'm building Azure Function (Premium plan) with Private endpoint.
As I'm using private endpoint, function is not available from the public internet / MSFT managed Cloud pipelines.
Now, idea was to use Deployment Center in Function App to enable CI/CD, but I'm failing to find a way how to script configuration of Deployment Center.
Is there even a way to setup Deployment Center configuration outside of Azure Portal? Using Bicep or Powershell? Essentially, something which will map repository/branch/build pipeline with given slot.
It will be weird to have completely automated process for deployment of infrastructure and then to go there and manually update deployment configuration for each subscription/stage.
you can use github actions to deploy the function, but you have to connect the github to the function through the deployment center.
This is simple process where in deployment center just select github under source and connect the github repository by Loging in the github account.
Another solution would be to use visual studio like tool to directly deploy from to development environment.
Also, you can containerize the function and deploy the container.
Refer the following documentation on all the ways of deployment to the azure.
I have 2 .NET 5 Azure Function Visual Studio projects . These 2 Functions to be deployed in a single Azure Function App.
I have 2 separate Build Pipelines for each of the projects and have separate Release Pipelines as well in Azure DevOps. I am not using YAML for release pipelines but depends on DevOps UI to choose a new Release pipeline.
My issue is that whenever running the Release pipeline, the last Release overrides the existing Function in Azure Function App. So, I am not getting 2 Functions as expected under a single Azure Function App. Always the last release deployment exists in Azure. Why one release deployment overrides existing Functions, even though they are from different Release pipelines?
In the MS documentation it states that if you perform a "Zip Deployment" to an Azure Function, it will always overwrite what is running on the Azure Function Service. I presume that the "Classic Pipeline" gives you the "Zip Deployment" option.
Link to MS Documentation: https://learn.microsoft.com/en-us/azure/devops/pipelines/tasks/deploy/azure-function-app?view=azure-devops#deployment-methods
For the moment, I do have a ticket open at Microsoft on how to manage different apps on the same Azure Function service. I only want changes made to the specific app where there are code changes without impacting any other existing apps on the Azure Function. For now, I only had one troubleshooting session with no solution in sight. I will share more information once I have received a solution/workaround.
I’m trying to configure an Azure logic apps with an Azure Devops connector that would create a new pipeline release
The pipeline needs two variables, system and scope:
And looking at the azure DevOps connector doc
https://learn.microsoft.com/en-us/connectors/visualstudioteamservices/#create-a-new-release
How should I configure the name and value in the logic app ?, I tried this but it didn't work:
How to pass those variable to the release pipeline in Azure DevOps ?
Apparently adding the connector from Visual studio will give an incomplete connector, deleting it and recreated it from the portal gave the key and value options
I have created Azure Data Factory with Copy Activity using C# and Azure SDK.
How can deploy it using CI/CD ?
Any URL or link will help
Data Factory continuous integration and delivery is now possible with directly through the web user interface using ARM Templates or even Git (Github or Azure DevOps).
Just click on "Set up Code Repository" and follow the steps.
Check the following link for more information, including a video demostration: https://aka.ms/azfr/401/02
One idea that I got from Microsoft was that using the same Azure SDK you could deserialize the objects and save down the JSON files following the official directory structure into your local GitHub/Git working directory
In other words you would have to mimic what the UI Save All/Save button does from the portal.
Then using Git bash, you can just commit and push to your working branch (i.e. develop) and from the UI you can just publish (this will create an adf_publish release branch with the ARM objects)
Official reference for CI using VSTS and the UI Publish feature: https://learn.microsoft.com/en-us/azure/data-factory/continuous-integration-deployment
Unfortunately, CI/CD for ADF is not very intuitive at first glance.
Check out this blog post where I'm describing what/how/why step by step:
Deployment of Azure Data Factory with Azure DevOps
Let me know if you have any questions or concerns and finally - if that works for you.
Good luck!
My resources on how to enable CI/CD using Azure DevOps and Data Factory comes from the Microsoft site below:
Continuous integration and delivery (CI/CD) in Azure Data Factory
I am still new to DevOps and CI/CD, but I do know that other departments had this set up and it looks to be working for them.
In Visual Studio Team Services, I would like to specify the Azure Subscription via a variable (see image below). The reason for this is that our ops team maintains the NON-PROD and PROD environments on different subscriptions.
However, when I do this I get the following in the log:
##[section]Starting: Azure App Service Deploy: XXXXfunc
==============================================================================
Task : Azure App Service Deploy
Description : Update Azure App Service using Web Deploy / Kudu REST APIs
Version : 2.1.10
Author : Microsoft Corporation
Help : [More Information](https://aka.ms/azurermwebdeployreadme)
==============================================================================
[RESOURCE_NAME] exists false
##[warning]Can\'t find loc string for key: CouldnotfetchacccesstokenforAzureStatusCode
##[error]CouldnotfetchacccesstokenforAzureStatusCode 401 Unauthorized
##[section]Finishing: Azure App Service Deploy: XXXXfunc
If I set the subscription using the drop down, then it all works fine.
Is this possible to do? If so, how?
UPDATE:
I am using App Service here as a simple example, but I also have a collection of Azure PowerShell tasks joined into a single Task Group. Each of these tasks need to have the subscription specified. If I can't pass a Azure sub in, then I'll have to either clone the Task Group or just list each step individually.
Its easier (and fits with how the system has been designed), if instead of this, you just use the Releases workflow to setup your dev/test environment, with the app service deploy pointing at that subscription, then clone that environment, call the new one "prod", and modify the release step in that environment to point at the other subscription. You can then also add governance (ie. email approval processes) around the build and deploy, and ensure the exact same build artifact is deployed to both environments, but when you want them to. I wrote a blog post last year to take you through this step by step, see https://russellyoung.net/2016/11/09/continuous-deployment-of-a-asp-net-core-app-to-azure-using-vsts/