Transition all core pipelines to `1es-templates`

[scbedd]

Pre-req work

• Prototype a working conversion of the primary stages templates in each repo. Ensure release works on each of these. Ensure that the builds are green without failing injected steps.
  • [x] azure/azure-sdk-for-python
    • Changeset
  • [x] azure/azure-sdk-for-net
    • Changeset
  • [x] azure/azure-sdk-for-java
    • Changeset
  • [x] azure/azure-sdk-for-js
    • Changeset
  • [x] azure/azure-sdk-for-go
    • Changeset
  • [x] azure/azure-sdk-for-c
    • ChangeSet
  • [x] azure/azure-sdk-for-cpp
    • ChangeSet
  • [x] azure/azure-sdk-for-ios
    • ChangeSet
  • [x] azure/azure-sdk-for-android
  • [ ] azure/azure-sdk

Rollout

There are necessary eng/common changes that need to roll out with these changes. To ensure easy rollout without breaking compatibility, perhaps the necessary pool and job changes should be done alongside the eng/common changes. That means

1. ~~Submit eng/common changes to azure/azure-sdk-tools. ~~
2. Let eng/common pipelines submit PRs to each repo
3. Apply changes from 1es-template-conversion branches from each repo to the eng/common branch.
4. Ensure all pipelines pass the common template release from each eng/common PR branch.
5. Merge them all, following the eng/common merge strategy for azure-sdk-tools as well.

The above was judged too risky. Decided to go with a bit slower, but safer approach of:

1. Submit PR to eng/common w/ new generation logic (hardcoded OS) and 1es publish
2. Work through repos one at a time, integrating the new eng/common changes into 1es-template-conversion

Repo	code complete	template release	template livetests	core run	merged
azure/azure-sdk-for-python	✅	✅	✅	✅	✅
azure/azure-sdk-for-net	✅	✅	✅	✅	✅
azure/azure-sdk-for-java	✅	✅	✅	✅	✅
azure/azure-sdk-for-js	✅	✅	✅	✅	✅
azure/azure-sdk-for-go	✅	✅	✅	✅	✅
azure/azure-sdk-for-c	✅	✅	✅	✅	✅
azure/azure-sdk-for-cpp	✅	✅	✅	✅	✅
azure/azure-sdk-for-ios	✅	✅	✅	✅	✅

Note: azure-sdk-for-net has merge blocked on a 1es-templates limitation.

Designer Builds

The following builds are designer, and will not benefit from the yml updates above.

• mgmt-netsdk-sign
• mgmt-NetCore-SDK-Publish
• mgmt-netsdk-multiapi-publish
• mgmt-netsdk-sdkcommon-publish
• mgmt-netsdk-publish
• Specs Repo - Update readme.md all-api-versions tags.
• Autorest Npm Admin Task
• tools - Codex - vscode.dev

We need to come up with a strategy for these.

Release Builds

Need to come up with a strategy for all the internal release pipelines that do not have yaml attached to them. Full List

[scbedd]

Creating a new issue for long tail items.