How to publish a pipeline trigger?

krunal 20 Reputation points
2024-04-27T16:09:57.06+00:00

I designed a pipeline in Azure Synapse that includes a copy activity within a for-each activity. The pipeline runs smoothly during debugging, but after integrating a trigger and committing changes to Azure DevOps, I can't find the pipeline. When I try to manually trigger it, I'm asked to "publish" the pipeline. Is there an extra step required to publish a pipeline trigger after committing changes to Azure DevOps?

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,485 questions
0 comments No comments
{count} votes

Accepted answer
  1. Harishga 4,250 Reputation points Microsoft Vendor
    2024-04-27T16:46:50.37+00:00

    Hi @krunal
    Thank you for reaching out to the community forum with your query. It seems that you are facing an issue with locating a pipeline after integrating a trigger and committing changes to Azure DevOps. You are prompted to "publish" the pipeline, despite using Azure DevOps.

    In order to perform a trigger run, you need to publish your changes. Only committing the changes doesn't suffice.

    Please check the official documentation here:
    https://learn.microsoft.com/en-us/azure/data-factory/how-to-create-schedule-trigger?tabs=data-factory
    Hope this helps. Do let us know if you any further queries.


    If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

    1 person found this answer helpful.
    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Patchfox 3,791 Reputation points
    2024-04-27T16:44:08.7766667+00:00

    Hi krunal, I want to help you with this question.

    To verify, your question: you created an Azure Synapse (Azure Fabric) pipeline that's copying data in a for-each-loop. While you debugging, the executions work. But after you integrate it with Azure Devops you can't find a pipeline and the trigger doesn't work.

    As you assume, after committing changes to Azure DevOps, you need to publish your pipeline. Publishing ensures that the latest changes are available for execution.

    I hope this will help you to solve your problem


    If the reply was helpful, please don’t forget to upvote or accept it as an answer, thank you!

    0 comments No comments