1ES Transition Items - "Extras"

[scbedd]

Discovered long tail items

• [x] Transition azure-sdk-for-android
• [x] Scan azure-sdk-build-tools exes with 1es-templates -> Remaining to be resolved:
  • [x] tools/sdk-generation-pipeline/ci.yml
  • [x] tools/oav-traffic-converter/ci.yml
  • [x] tools/mock-service-host/ci.yml
  • [x] tools/js-sdk-release-tools/ci.yml
  • [x] tools/apiview/parsers/js-api-parser/ci.yml
  • [x] tools/apiview/emitters/typespec-apiview/ci.yml
  • [x] eng/pipelines/templates/stages/archetype-autorest-preview.yml
  • [x] tools/tsp-client/ci.yml
• [x] Remove download-credscan-suppression.yml in favor of disabling the SDL step on specific jobs or the like
  • We can account for the places where the clone is in a different location than the default SDL config by utilizing a templateContext argument on the deployment. Otherwise I'm not certain we can bypass this.
  • We CAN disable sdl injected steps when there is no checkout. Unfortunately during our signing stage there absolutely is checkout. Second section on this page This is for the entire SDL stage, not the injected steps during artifact publish.
  • No way to disable this. Only possible thing we could change is update to generate a blank credscan suppression file, then simply reference that via templateContext override.

    • templateContext:
      sdl:
      credscan:
        suppressionsFile: path/to/generated/file.json

• [ ] Eliminate warning for 1es artifact of that name already exists for matrix-ed test jobs This issue has drug on for 3 weeks with new discovered work. Going to file this as its own thing and pursue it.

yml Builds

• [x] openapi-alps-PullRequest - One branch already compliant. Not shipped to 3rd parties.
• [x] openapi-alps-publish -- PR
• [x] openapi-alps-ci Not used as artifact source for release.
• [x] public.avocado - PR
  • Will create internal build for release phase.
• [x] public.openapi-diff - PR
  • Will create internal build for release phase.
• [x] public.rest-api-specs-scripts
  • Deprecated repo. Likely no-op here.
• [x] Azure.git-rest-api Build
  • This can probably be removed after we swap to releasing using ESRP task. Just going to ignore this for now.
• [x] oav-merge-validation - PR
• [x] regression-tests-full - PR
• [x] AutoRest - Publish - Azure/autorest - only missing ESRP. Going to ignore for now.

Designer Builds

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

• [x] mgmt-netsdk-sign. Not used since 2019, can't clean up due to release. Disabled.
• [x] mgmt-NetCore-SDK-Publish
• [x] mgmt-netsdk-multiapi-publish
• [x] mgmt-netsdk-sdkcommon-publish
• [x] mgmt-netsdk-publish
• [x] Specs Repo - Update readme.md all-api-versions tags.
• [x] Autorest Npm Admin Task Supplanted by npm admin build
• [x] tools - Codex - vscode.dev

Anything crossed out is deleted. Checkmark otherwise indicates merged PR.

Release Builds

• [x] azuresdkpartnerdrops to pypi - esrp release - PR
• [x] APIVIew UI Test instance - PR
• [x] Release to APIView staging - PR
• [x] APIView to Azure App Service - PR
• [x] azuresdkpartnerdrops to npm - PR
• [x] azure-openapi-validator to npm - PR
• [x] azure-openapi-validator to npm - staging - PR
• [x] azure-uamqp-python - client to pypi - PR
• [x] Publish to npmjs.com (windowsazure) - PR
• [x] js - tools to npm - publish (@azure)
  • Avocado
  • oad
  • public.rest-api-specs-scripts
  • We have transitioned the source of this package from the public repo here to the internal repo here.
• [x] kebab-container-app-release -- PR
  • Feeds off of openapi-publish

Need to mark as non-production or otherwise transition each of the above builds. At the very minimum the release builds need to be transitioned to yml.

[kurtzeborn]

These designer builds are lo-pri... they existed before and they continue to exist after the transition. We should not worry about these until we get dinged on them (and then we'll probably just delete them).

[alzimmermsft]

At least in Java we're finding that in some CI runs virus scanning can take 10 to 15 minutes to run. Looking at the step running virus scanning, this could be that we're using '$(System.DefaultWorkingDirectory)' as the output parent directory, which may mean we're scanning all source code, build artifacts, and test recordings downloaded and generated during CI.

We should investigate if moving these build artifacts to a subfolder reduces the number of files that need to be virus scanned.

[scbedd]

These designer builds are lo-pri... they existed before and they continue to exist after the transition. We should not worry about these until we get dinged on them (and then we'll probably just delete them).

They were all deleted.

[scbedd]

This is all done except for one item that I am blocked on. Publishing the ADO extension from openapi-alps-publish. Have a support ticket out with the 1es folks. Holding pattern until response.