disable orginal pipeline for mgmt in main branch

[dw511214992]

change the trigger in mgmt-ci.yml and mgmt-pr.yml to disable it in main branch (we will release track1 sdk in branch feature/v4)

[weshaggard]

Do we not want to build any track 1 libraries in main at all? Would it make sense to just delete this yml file from main?

[ramya-rao-a]

Do we not want to build any track 1 libraries in main at all? Would it make sense to just delete this yml file from main?

There are still Track 1 data plane auto generated libraries in the main branch. They use the same pipeline

[dw511214992]

Do we not want to build any track 1 libraries in main at all? Would it make sense to just delete this yml file from main?

There are still Track 1 data plane auto generated libraries in the main branch. They use the same pipeline

@ramya-rao-a If there are still track1 dataplane libraries based on this pipeline, can we release them in another branch like mgmt libraries?

[weshaggard]

My suggestion is to close this PR and use the generic set of filters I called out in #15993 in both main and everywhere else.

[dw511214992]

My suggestion is to close this PR and use the generic set of filters I called out in #15993 in both main and everywhere else.

@weshaggard I hope to release track1 sdk in branch feature/v4 and the main branch is only for track2 sdk. So we need to disable the original pipeline for track1 in main branch.

[weshaggard]

This will likely break any scheduled or ci triggers on the existing pipelines so you will want to make sure to update those in DevOps.

[dw511214992]

This will likely break any scheduled or ci triggers on the existing pipelines so you will want to make sure to update those in DevOps.

@weshaggard yes. I have make changes to the following ci triggers/release pipeline in devops:
https://dev.azure.com/azure-sdk/public/_build?definitionId=525
https://dev.azure.com/azure-sdk/internal/_release?_a=releases&view=mine&definitionId=42
https://dev.azure.com/azure-sdk/public/_build?definitionId=138&_a=summary

As far as I know, I thnk only these 3 pipelines are for track1 mgmt sdk. If there are any pipeline I missed, please let me know.

[ramya-rao-a]

If there are still track1 dataplane libraries based on this pipeline, can we release them in another branch like mgmt libraries?

I hope to release track1 sdk in branch feature/v4 and the main branch is only for track2 sdk. So we need to disable the original pipeline for track1 in main branch.

Releasing the handful Track 1 auto generated data plane packages from a separate branch is an overhead I would like to avoid. Can we not keep this pipeline for the main branch, but remove all the mgmt plane packages from the include list?

cc @qiaozha