I have pipeline and I deployed azure functions from it and I want to disable the pipeline for few days and reenable when I use it
Not only azure functions you can create any pipeline, but you can also disable and re enable it whenever required
Under pipeline settings you can find the options of deleting the pipeline
Related
I have a YAML pipeline in Azure DevOps that contains a list of variables which I can choose which on of them to use in runtime.
This is my code:
And this is how it looks in runtime:
My question is how to create this option in a classic Azure pipeline?
From past threads I read I saw that there's no option to do that, but maybe something changed lately.
Not Possible with Classic Release Pipeline.
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 am looking for some best practices and suggestions:
My team is creating an Azure DevOps pipeline to deploy a complex infrastructure of VNets, VMs, Azure ML workspaces, SQL databases, etc.
The pipeline uses Terraform where possible, but Powershell or AZ CLI where needed.
The pipeline works, it is version controlled, it has proper unit tests and integration tests (or at least decent ones).
However, due to the instability of Azure resourcing sometimes the pipeline will fail because, for instance:
SQL server provisioning fails
AD join of VMs fails
or other activities which are not due to bad Infra as Code, but rather the stochasticity of the task. Provisioning resources is inherently unstable, similar to networking, etc.
I am not complaining about Azure. I am just asking:
How can I adjust the IaC pipeline so that when Azure fails occur, some sort of retry can automatically be triggered?
As a concrete example, is there an Azure or Terraform equivalent to Python's tenacity package or Java's Spring Retry?
How can I adjust the IaC pipeline so that when Azure fails occur, some sort of retry can automatically be triggered?
You could try to use Trigger Azure DevOps Pipeline task to trigger current build pipeline automatically when the build failed.
To be able to use the extension an Azure DevOps API endpoint needs to be created.
For the service connection to work as it should you need to configure the following parameters:
Organization Url: The URL of the organization.
(https://dev.azure.com/[organization])
Personal Access Token: The personal access token.
Besides, we need to set the condition for this task, which will trigger the current pipeline Only when a previous task has failed:
I am using Azure DevOps pipeline to run some jobs. This pipeline has been created using YML.
As I am calling to Azure data factory pipeline using my DevOps pipeline, so if a user manually cancell DevOps pipeline, in that case my Azure Data Factory still in running mode which should ideally not happened.
Is there a way to stop my azure data factory pipeline autmatically whenever there is cancellation of Azure DevOps pipeline from UI?
As a workaround, We could add task power shell task and set the custom condition canceled(), this task will only run if you cancel the build.
Then add power shell script to call the API to cancel the Azure Data Factory pipeline.
POST https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.DataFactory/factories/{factoryName}/pipelineruns/{runId}/cancel?api-version=2018-06-01
Also, we could do this via webhook, you could also check this blog and update the json.
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