Use breadcrumbfiles associated with each asset, versus shared

[scbedd]

See title. This addresses the issues that were temporarily mitigated by this .NET PR.

[benbp]

Is this going to have any conflicts when people upgrade locally? i.e. if the new proxy ignores the existing old breadcrumb file, will it try to overwrite stuff or use different paths? I don't fully understand the "pre-breadcrumb file" behavior.

[scbedd]

Is this going to have any conflicts when people upgrade locally? i.e. if the new proxy ignores the existing old breadcrumb file, will it try to overwrite stuff or use different paths? I don't fully understand the "pre-breadcrumb file" behavior.

It'll write new ones now. Should be seamless upgrade.

[scbedd]

/azp run tools - test-proxy - tests

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[scbedd]

Is this going to have any conflicts when people upgrade locally? i.e. if the new proxy ignores the existing old breadcrumb file, will it try to overwrite stuff or use different paths? I don't fully understand the "pre-breadcrumb file" behavior.

It'll write new ones now. Should be seamless upgrade.

However, thinking about this over the afternoon, this upgrade will require an update of the transition script + documentation. My current plan is to

1. Get this tested and entirely green and merged.
2. In the same PR that I bump the version of the proxy in, I'll also update the migration script resources under eng/common/testproxy/transition-script/. We were also asking that I move it under onboarding as well. I may as well knock out all of that at the same time while I touch the script.

[scbedd]

/azp run tools - test-proxy - tests

[azure-pipelines]

No commit pushedDate could be found for PR 6604 in repo Azure/azure-sdk-tools

[scbedd]

/azp run tools - test-proxy - tests

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[scbedd]

/azp run tools - test-proxy - tests

[azure-pipelines]

No commit pushedDate could be found for PR 6604 in repo Azure/azure-sdk-tools

[scbedd]

/azp run tools - test-proxy - tests

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[scbedd]

No commit pushedDate could be found for PR 6604 in repo Azure/azure-sdk-tools

What does this even mean devops bot!?

[scbedd]

/azp run tools - test-proxy - tests

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[scbedd]

/azp run tools - test-proxy - tests

[azure-pipelines]

No commit pushedDate could be found for PR 6604 in repo Azure/azure-sdk-tools

[scbedd]

/azp run tools - test-proxy - tests

[azure-pipelines]

No commit pushedDate could be found for PR 6604 in repo Azure/azure-sdk-tools

[scbedd]

/azp run tools - test-proxy - tests

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).