Skip breaking change detection in release pipeline

[msyyc]

We plan to adopt breaking changes tool when generating SDK so that we could recognize potential SDK breakings in advance. However, when open it for Mgmt SDK, it blocks SDK release so I have to revert it in #36104.

I understand one solution is follow https://github.com/Azure/azure-sdk-for-python/tree/main/scripts/breaking_changes_checker#types-of-breaking-changes-detected to suppress each breaking item but it is not flexible. Is there any way I can only adopt the tool but not block SDK release?

[raych1]

@catalinaperalta
to integrate into the spec PR pipeline, the breaking change tool must support the detection within a specific service scope. This could be achieved by passing the service name when running the command of breaking change tool.

[catalinaperalta]

@catalinaperalta to integrate into the spec PR pipeline, the breaking change tool must support the detection within a specific service scope. This could be achieved by passing the service name when running the command of breaking change tool.

The tool is scoped to run within a specific sdk directory. Let me know if that's not what you meant

[catalinaperalta]

@msyyc I'm thinking we could probably suppress all change reports for a specific library but you wont see what the breaking changes are for that library in the pipeline. Or do you want the pipeline not to block on the breaking changes check? I think the pipeline configuration should be changed in that case.

[msyyc]

@catalinaperalta I find the way to disable breaking change:

azure-sdk-for-python/eng/pipelines/templates/steps/run_breaking_changes.yml

Lines 12 to 24 in 14dd582

	steps:
	- task: PythonScript@0
	displayName: 'Run Breaking Changes'
	inputs:
	scriptPath: 'scripts/devops_tasks/dispatch_tox.py'
	arguments: >-
	"$(TargetingString)"
	--mark_arg="${{ parameters.TestMarkArgument }}"
	--service="${{ parameters.ServiceDirectory }}"
	--toxenv="breaking"
	--disablecov
	env: ${{ parameters.EnvVars }}
	condition: and(succeededOrFailed(), ne(variables['Skip.BreakingChanges'],'true'))

. We just need to set Skip.BreakingChanges as true then this step shall be skipped.
Let me check it and if it works, I will close this issue.

[catalinaperalta]

@msyyc did your solution work?

[msyyc]

I will try it after #36601 merged