Question about a best practice inside Azure DevOps for Azure Synapse

Jonathan Sus 0 Reputation points
2023-02-07T14:02:36.44+00:00

Hi there,

I've one question about a best practice inside Azure DevOps for Azure Synapse, this is for make the CI part of the CICD, I've followed this link: https://techcommunity.microsoft.com/t5/data-architecture-blog/ci-cd-in-azure-synapse-analytics-part-3/ba-p/1993201 to create the CI pipeline and the CD (Release pipeline) in one project and it works ok, but now I've another project where they doesn't have a folder inside the "main" branch of the repo with the templates of the Synapse Pipeline, they only have this templates inside the workspace_publish folder.

I saw a few videos about this CICD and some people configures the CI pipeline with the workspace_publish as the default branch for manual and scheduled builds, but in that link he takes this other folder created in the main branch for this operation.

By the way, I don't know how the guys of the first project have created this folder with the same templates than the workspace_publish, I know when they click in the publish button Synapse creates this templates, but this is created 2 times or is the same folder with a direct access.

I'm a little confused, what is the best practice to do this?

Azure Synapse Analytics
Azure Synapse Analytics
An Azure analytics service that brings together data integration, enterprise data warehousing, and big data analytics. Previously known as Azure SQL Data Warehouse.
4,395 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. ShaikMaheer-MSFT 37,896 Reputation points Microsoft Employee
    2023-02-08T10:24:36.18+00:00

    Hi Jonathan Sus,

    Thank you for posting this query in Microsoft Q&A Platform.

    workspace_publish branch actually contains your ARM templates. That means template for your entire workspace.

    You mentioned inside main branch they don't have folder for synapse pipelines. What you mean by this? You mean folder is missing inside collaboration branch(main) with Synapse Pipeline Json's? If yes, when you connect your workspace with Git again, try to import resources from there.

    Your first project people might have connected Workspace in past with Git repo and tried publishing. That way workspace_publish branch might have got created. Please note, we can change this default behavior to some other branch too from settings inside Git configuration menu under manage tab in your workspace.

    Please check below video, of CI/CD of mine which explains for ADF for better idea. It's almost similar with Synapse also. In case, of ADF it creates adfpublish branch. In case of Synaspe it creates workspace_publish branch.

    Continuous integration and deployment in Azure Data Factory

    Hope this helps. Please let me know if any further queries.

    Please consider hitting Accept Answer button. Accepted answers help community as well.

    1 person found this answer helpful.