Skip to content

cicd-overview.md

Latest commit

 

History

History
39 lines (26 loc) · 2.26 KB

cicd-overview.md

File metadata and controls

39 lines (26 loc) · 2.26 KB
title Continuous integration and continuous deployment
description This article gives an overview of setting up a continuous integration and deployment (CI/CD) pipeline for Azure Stream Analytics jobs.
author alexlzx
ms.author zhenxilin
ms.service azure-stream-analytics
ms.topic how-to
ms.date 01/23/2025

Continuous integration and continuous deployment (CI/CD) of Stream Analytics jobs

You can build, test, and deploy your Azure Stream Analytics (ASA) job using a source control integration. Source control integration creates a workflow in which updating code would trigger a resource deployment to Azure. This article outlines the basic steps for creating a continuous integration and continuous delivery (CI/CD) pipeline.

Create a CI/CD pipeline

Follow the steps to create a CI/CD pipeline for your Stream Analytics project:

  1. Create a Stream Analytics project using VS Code. You can either create a new project or export an existing job to your local machine using the ASA Tools extension for Visual Studio Code.

  2. Commit your Stream Analytics project to your source control system, like a Git repository.

  3. Use Azure Stream Analytics CI/CD tools to build the projects and generate Azure Resource Manager templates for the deployment.

  4. Run automated script tests for quality regression.

  5. Deploy the job to Azure automatically.

Auto build, test, and deploy

You can use the command line and Azure Stream Analytics CI/CD tools to auto build, test, and deploy. You can also set up a CI/CD pipeline in Azure Pipelines. Azure Pipelines to enable more advanced capabilities, such as pipeline management, visualization, and triggers.

Related content